Triple
T31106926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outpost 32 |
E792817
|
entity |
| Predicate | associatedTitan |
P207355
|
FINISHED |
| Object | King Ghidorah |
E94581
|
NE 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: King Ghidorah | Statement: [Outpost 32, associatedTitan, King Ghidorah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTitan Context triple: [Outpost 32, associatedTitan, King Ghidorah]
-
A.
associatedMob
Indicates a relationship where one entity is linked or connected to a particular mob (mobile entity), typically as its counterpart, partner, or related unit.
-
B.
associatedRocket
Indicates that one entity is linked or connected to a particular rocket, typically as its counterpart, carrier, or related vehicle.
-
C.
associatedMine
Indicates that one entity is linked or connected to a particular mine, typically as its source, location, or relevant mining site.
-
D.
associatedTomb
Indicates a relationship in which an entity is linked to or connected with a particular tomb, such as by burial, ownership, dedication, or commemoration.
-
E.
associatedDam
Indicates a relationship where one entity is linked or connected to a specific dam, typically as its related or corresponding dam structure.
- F. None of above. chosen
Provenance (5 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b07524948819081a16841f5fb6ccb |
completed | June 11, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:03 p.m.