Triple
T17334647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrowhead |
E420904
|
entity |
| Predicate | hasUniverseType |
P117521
|
FINISHED |
| Object | high fantasy |
—
|
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: high fantasy | Statement: [Arrowhead, hasUniverseType, high fantasy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUniverseType Context triple: [Arrowhead, hasUniverseType, high fantasy]
-
A.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
B.
inUniverseProductType
Indicates that a product belongs to or is categorized within a specific fictional or defined universe or setting.
-
C.
hasFictionalUniverseType
chosen
Indicates that an entity is associated with, or belongs to, a particular type or category of fictional universe.
-
D.
hasInUniverseFormat
Indicates that something is presented or expressed in a specific format as it exists within a particular fictional or conceptual universe.
-
E.
inUniverseLocationType
Indicates the type or category of location that something occupies within a fictional or defined 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a1125d88190b67243b30d93ce1c |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.