Triple
T28375778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red the Fire Truck |
E718751
|
entity |
| Predicate | ownerUniverse |
P41009
|
FINISHED |
| Object | Disney |
—
|
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: Disney | Statement: [Red the Fire Truck, ownerUniverse, Disney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerUniverse Context triple: [Red the Fire Truck, ownerUniverse, Disney]
-
A.
inUniverseOwner
Indicates that one entity is the canonical or official owner of another entity within a specific fictional or defined universe or continuity.
-
B.
associatedUniverse
chosen
Indicates that one entity is linked or belongs to a particular universe, realm, or overarching world context.
-
C.
inUniverseUser
Indicates that a user exists or participates within a specified fictional or conceptual universe.
-
D.
inUniverseOwnerSpecies
Indicates that a particular species is recognized as the canonical or in-universe owner of something within a fictional or defined universe.
-
E.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 1:03 a.m.