Triple
T29723344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Shatterdome |
E752115
|
entity |
| Predicate | equipmentTypeHoused |
P13867
|
FINISHED |
| Object | Jaeger |
—
|
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: Jaeger | Statement: [Tokyo Shatterdome, equipmentTypeHoused, Jaeger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentTypeHoused Context triple: [Tokyo Shatterdome, equipmentTypeHoused, Jaeger]
-
A.
hostsUnitType
chosen
Indicates that one entity serves as a location or platform that accommodates or contains a specified type of unit.
-
B.
typeOfEquipmentManaged
Indicates the specific kind or category of equipment that an entity is responsible for managing.
-
C.
equipmentTypeProduced
Indicates that an entity produces or manufactures a particular type or category of equipment.
-
D.
typeOfEquipmentUsed
Indicates that a particular piece or category of equipment is utilized in performing a specific action, process, or activity.
-
E.
equipmentTypeTrainedOn
Indicates the type of equipment on which an entity has received training or is qualified to operate.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672fd06bc81909ba03a0edde617ce |
completed | May 2, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:37 p.m.