Triple
T23574269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travelers |
E580203
|
entity |
| Predicate | futureSetting |
P125914
|
FINISHED |
| Object | dystopian 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: dystopian future | Statement: [Travelers, futureSetting, dystopian future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureSetting Context triple: [Travelers, futureSetting, dystopian future]
-
A.
futureSettingCharacteristic
chosen
Indicates that a characteristic or property is expected to hold for an entity in a future setting or time.
-
B.
futureServes
Indicates that, at a future time, one entity will perform a service or act in a serving role for another entity.
-
C.
futureSiteOf
Indicates that a location is planned or designated to become the site of a particular entity or structure in the future.
-
D.
futureComponentOf
Indicates that one entity is expected or planned to become a component or part of another entity at some point in the future.
-
E.
futureChangeRequires
Indicates that a planned or upcoming modification is contingent upon, or must be preceded by, another specified condition, action, or change.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd4cde48190b5e4eb162d772319 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:37 p.m.