Triple
T1709363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nate Lambert |
E36941
|
entity |
| Predicate | setInFictionalTime |
P11197
|
FINISHED |
| Object | near future |
—
|
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: near future | Statement: [Nate Lambert, setInFictionalTime, near future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInFictionalTime Context triple: [Nate Lambert, setInFictionalTime, near future]
-
A.
setInFictionalLocation
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
-
B.
timeTravelTo
Indicates traveling from one point in time to another, typically different, point in time.
-
C.
fictionalEra
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
-
D.
timeOfNarrative
chosen
Indicates the specific time or period during which the events of a narrative are set or unfold.
-
E.
timeTravelMethod
Indicates the specific mechanism or technique by which an entity performs or experiences time travel.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab7521878c8190b9e7739b8c3fc705 |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61bd46d48190915500d75a9d8e94 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.