Triple
T36628595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Famous Forty Oz books |
E904242
|
entity |
| Predicate | definesCanonFor |
P13648
|
FINISHED |
| Object | traditional Oz fandom |
—
|
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: traditional Oz fandom | Statement: [Famous Forty Oz books, definesCanonFor, traditional Oz fandom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesCanonFor Context triple: [Famous Forty Oz books, definesCanonFor, traditional Oz fandom]
-
A.
inCanonWith
Indicates that two or more works, events, or elements are officially recognized as belonging to the same narrative continuity or canon.
-
B.
usesCanon
Indicates that one entity employs or relies on another entity as its standard, reference, or authoritative source.
-
C.
canonType
Indicates the classification of something according to its status or role within an official or accepted canon.
-
D.
givesCanon
chosen
Indicates that one entity provides or establishes an official or authoritative version (canon) of something for another entity or context.
-
E.
inCanonOf
Indicates that one entity is officially recognized as part of the established canon or authoritative body of works associated with another entity.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
Created at: May 3, 2026, 4:11 p.m.