Triple
T6355932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrott Transportation Center |
E142989
|
entity |
| Predicate | hasCanopiesOverPlatforms |
P8429
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Arrott Transportation Center, hasCanopiesOverPlatforms, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanopiesOverPlatforms Context triple: [Arrott Transportation Center, hasCanopiesOverPlatforms, yes]
-
A.
hasCanopy
chosen
Indicates that one entity possesses or is characterized by a canopy associated with it.
-
B.
hasSidePlatforms
Indicates that something is equipped with platforms located on its sides, typically for access, support, or operation.
-
C.
hasSubsurfacePlatforms
Indicates that an entity includes or is equipped with platforms located below the surface or underground.
-
D.
hasNumberOfPlatforms
Indicates the relationship that specifies how many platforms are associated with a given entity.
-
E.
hasAdvancedTerrain
Indicates that an entity possesses or is associated with terrain featuring complex, challenging, or enhanced physical characteristics beyond standard ground conditions.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067e22c00819089bc68efb85bc2c8 |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.