Triple
T35605501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shannon Christie |
E1028876
|
entity |
| Predicate | yearOfFictionalSetting |
P180185
|
FINISHED |
| Object | 1892 |
—
|
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: 1892 | Statement: [Shannon Christie, yearOfFictionalSetting, 1892]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfFictionalSetting Context triple: [Shannon Christie, yearOfFictionalSetting, 1892]
-
A.
periodOfFictionalSetting
chosen
Indicates the time period in which the events of a fictional work are set.
-
B.
launchedInFictionalYear
Indicates that an entity is depicted as being launched in a specified fictional or imaginary year within a narrative or fictional universe.
-
C.
endsInFictionalYear
Indicates that an event, story, or timeline concludes in a year that exists only within a fictional or imagined setting.
-
D.
foundedInFictionalYear
Indicates that an entity was established or created in a year that exists only within a fictional or imaginary timeline, rather than in real-world history.
-
E.
fictionalYearBuilt
Indicates the year in which a fictional structure, place, or object is described as having been built within its narrative or fictional context.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: May 3, 2026, 4:05 p.m.