Triple
T26304844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J line |
E661651
|
entity |
| Predicate | runsThroughStructureType |
P5886
|
FINISHED |
| Object | underground |
—
|
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: underground | Statement: [J line, runsThroughStructureType, underground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsThroughStructureType Context triple: [J line, runsThroughStructureType, underground]
-
A.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
B.
approachStructureType
Indicates that one entity moves closer to or advances toward a specified type of structure.
-
C.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
D.
viaStructure
chosen
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
E.
rootStructure
Indicates that one entity serves as the primary or foundational structural element upon which another entity is based or organized.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 26, 2026, 10:18 p.m.