Triple
T30987044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Taylor |
E789555
|
entity |
| Predicate | settingEncountered |
P101818
|
FINISHED |
| Object | dystopian future Earth |
—
|
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 Earth | Statement: [George Taylor, settingEncountered, dystopian future Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingEncountered Context triple: [George Taylor, settingEncountered, dystopian future Earth]
-
A.
settingEncounter
chosen
Indicates that an encounter or interaction is taking place within a particular setting or environment.
-
B.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
C.
settingEvoked
Indicates that a particular setting or environment brings about, suggests, or calls to mind a specific response, mood, or association.
-
D.
encountered
Indicates that one entity came across or met another entity, typically in a specific place or context, often unexpectedly or during the course of some activity.
-
E.
settingOfAdventure
Indicates that a location or environment serves as the primary setting where an adventure takes place.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 8:56 p.m.