Triple
T32861616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | default mode network |
E840532
|
entity |
| Predicate | mostActiveDuring |
P86087
|
FINISHED |
| Object | rest |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: rest | Statement: [default mode network, mostActiveDuring, rest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostActiveDuring Context triple: [default mode network, mostActiveDuring, rest]
-
A.
hasTimeOfHighActivity
chosen
Indicates that an entity experiences its peak or most intense level of activity during a specified time period.
-
B.
activeAround
Indicates that an entity is performing actions or exhibiting activity in the vicinity of another entity or location.
-
C.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
-
D.
activityPeakPeriod
Indicates the time period during which an activity reaches its highest level or intensity.
-
E.
historicallyActiveIn
Indicates that an entity was active or engaged in significant activities within a particular place or context during a past historical period.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:17 a.m.