Triple
T31492778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Silver Chair |
E803451
|
entity |
| Predicate | hasFictionalWorld |
P138873
|
FINISHED |
| Object | Narnian universe |
—
|
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: Narnian universe | Statement: [The Silver Chair, hasFictionalWorld, Narnian universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalWorld Context triple: [The Silver Chair, hasFictionalWorld, Narnian universe]
-
A.
hasFictionalWorldType
Indicates that an entity is associated with, set in, or characterized by a particular type or category of fictional world.
-
B.
hasFictionalUniverseProperty
Indicates that a fictional universe possesses a specific characteristic, attribute, or property.
-
C.
hasFictionalUniverseStatus
Indicates that an entity holds a particular status or classification within a fictional universe or continuity.
-
D.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
E.
isSetInFictionalUniverse
chosen
Indicates that a narrative work takes place within a specific fictional universe or setting.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: April 30, 2026, 9:39 p.m.