Triple
T231747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AeroTrain |
E4424
|
entity |
| Predicate | accessibility |
P1710
|
FINISHED |
| Object | wheelchair accessible |
—
|
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: wheelchair accessible | Statement: [AeroTrain, accessibility, wheelchair accessible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessibility Context triple: [AeroTrain, accessibility, wheelchair accessible]
-
A.
accessible
chosen
Indicates that one entity can be reached, entered, used, or understood by another entity, often without undue difficulty or barriers.
-
B.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
C.
availability
Indicates that an entity is present, accessible, or ready for use or interaction by another entity.
-
D.
disability
Indicates that an entity has a physical, mental, or sensory impairment that substantially limits one or more major life activities.
-
E.
accessMode
Indicates the manner or method by which an entity can be accessed, used, or interacted with.
- 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_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. |
Created at: Feb. 28, 2026, 2:53 a.m.