Triple
T32284298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Snow |
E824782
|
entity |
| Predicate | wroteAboutFictionalUniverse |
P167393
|
FINISHED |
| Object | Land of Oz |
—
|
NE NERFINISHED |
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: Land of Oz | Statement: [Jack Snow, wroteAboutFictionalUniverse, Land of Oz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteAboutFictionalUniverse Context triple: [Jack Snow, wroteAboutFictionalUniverse, Land of Oz]
-
A.
fictionalUniverse
Indicates that two entities exist within, or are associated with, the same fictional universe or narrative setting.
-
B.
discussesFictionalUniverse
chosen
Indicates that one entity engages in discussion or analysis about the fictional universe associated with another entity.
-
C.
fictionalUniverseCreated
Indicates that one entity is the creator or originator of a particular fictional universe or setting in which stories or works take place.
-
D.
expandsFictionalUniverseOf
Indicates that one work adds new content, details, or dimensions to the fictional universe established by another work.
-
E.
fictionalUniverseAuthor
Indicates that an author is the creator or primary writer responsible for a given fictional universe.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcce457c819091b711d6cc66c980 |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:43 a.m.