Triple
T231721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AeroTrain |
E4424
|
entity |
| Predicate | guidewayType |
P9536
|
FINISHED |
| Object | underground guideway |
—
|
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 guideway | Statement: [AeroTrain, guidewayType, underground guideway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidewayType Context triple: [AeroTrain, guidewayType, underground guideway]
-
A.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
B.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
C.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
D.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
E.
tollingType
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
- F. None of above. chosen
Provenance (4 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b5a075081909b0e9b88c1492d5a |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25e06dd7c8190a8cbb76cee3c6e4b |
completed | Feb. 28, 2026, 3:16 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.