Triple
T29340904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-11 blaster rifle |
E744033
|
entity |
| Predicate | inUniverseLength |
P172388
|
FINISHED |
| Object | about 0.5 meters |
—
|
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: about 0.5 meters | Statement: [E-11 blaster rifle, inUniverseLength, about 0.5 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseLength Context triple: [E-11 blaster rifle, inUniverseLength, about 0.5 meters]
-
A.
universeNumber
Indicates that an entity is associated with a specific universe identified by a particular number or index.
-
B.
inUniverseAge
Indicates the age of an entity as measured within the timeline or continuity of a specific fictional or defined universe.
-
C.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
D.
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.
-
E.
inUniverseReference
Indicates that one entity makes a reference to another entity that exists within the same fictional or conceptual universe.
- F. None of above. chosen
Provenance (4 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 28, 2026, 1:33 p.m.