Triple
T36953212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | planet Sera |
E914126
|
entity |
| Predicate | subterraneanInhabitants |
P152891
|
FINISHED |
| Object | Locust Horde |
—
|
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: Locust Horde | Statement: [planet Sera, subterraneanInhabitants, Locust Horde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subterraneanInhabitants Context triple: [planet Sera, subterraneanInhabitants, Locust Horde]
-
A.
hasSubterraneanCreatures
chosen
Indicates that an entity contains, harbors, or is associated with creatures living beneath the ground or surface.
-
B.
subterranean
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
-
C.
burrowsIn
Indicates that one entity digs into and creates or occupies a tunnel or hole within another entity or medium.
-
D.
otherInhabitants
Indicates that there exist additional beings or residents associated with or present in the same place, group, or context as a referenced entity.
-
E.
hasUndergroundOrgan
Indicates that an entity possesses an organ or structure that is located below the ground surface.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.