Triple
T1400452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SkyPod |
E30767
|
entity |
| Predicate | locatedInStructureType |
P841
|
FINISHED |
| Object | concrete and steel communications tower |
—
|
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: concrete and steel communications tower | Statement: [SkyPod, locatedInStructureType, concrete and steel communications tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInStructureType Context triple: [SkyPod, locatedInStructureType, concrete and steel communications tower]
-
A.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
C.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
D.
hasStructureType
chosen
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
E.
locatedInGovernmentBody
Indicates that an entity is situated within, or is part of, a specific governmental body or institution.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c39c4c148190997150996ca26a99 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.