Triple
T3969781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Rock City |
E92300
|
entity |
| Predicate | temporality |
P53238
|
FINISHED |
| Object | temporary settlement |
—
|
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: temporary settlement | Statement: [Black Rock City, temporality, temporary settlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporality Context triple: [Black Rock City, temporality, temporary settlement]
-
A.
temporalAspect
Indicates the time-related characteristics or phase (such as duration, frequency, or temporal status) associated with an event or relationship.
-
B.
temporalEffect
Indicates a relationship where one event, state, or action produces consequences or changes that occur at a later time.
-
C.
timePerspective
Indicates how an entity conceptually relates to or orients itself toward time, such as focusing on past, present, or future.
-
D.
tempo
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
-
E.
temporalRelation
Indicates a relationship that specifies how two events or states are positioned relative to each other in time (e.g., before, after, or overlapping).
- F. None of above. chosen
Provenance (4 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefac8f7a48190b065487ce090eaf2 |
completed | March 9, 2026, 4:52 p.m. |
Created at: March 9, 2026, 3:32 p.m.