Triple
T17977502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rachel Salas |
E449513
|
entity |
| Predicate | fictionalUniverseWorkReleaseYear |
P110890
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Rachel Salas, fictionalUniverseWorkReleaseYear, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalUniverseWorkReleaseYear Context triple: [Rachel Salas, fictionalUniverseWorkReleaseYear, 2011]
-
A.
fictionalUniverseDebut
Indicates the first appearance of an entity within a particular fictional universe or continuity.
-
B.
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.
-
C.
endsInFictionalYear
Indicates that an event, story, or timeline concludes in a year that exists only within a fictional or imagined setting.
-
D.
novelReleaseYear
chosen
Indicates the calendar year in which a novel was first released or published.
-
E.
activeInFictionalYear
Indicates that an entity is active or operating during a specified fictional or imaginary year within a narrative or fictional timeline.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b200e9108190bcdde5ba7938ba94 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.