Triple
T1015106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunt Valley station |
E21911
|
entity |
| Predicate | hasADAAccess |
P23432
|
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: [Hunt Valley station, hasADAAccess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasADAAccess Context triple: [Hunt Valley station, hasADAAccess, yes]
-
A.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
B.
hasAccessModel
Indicates that one entity is permitted to use, interact with, or retrieve a particular model controlled by another entity or system.
-
C.
hasAdherent
Indicates that an entity is a follower, supporter, or member attached to another entity (such as a person, organization, belief, or movement).
-
D.
hasClearance
Indicates that one entity possesses the required authorization level or permission to access or perform actions on another entity or resource.
-
E.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c05060819083c51717874074c8 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7a0d0308190a00192aa9062bdaa |
completed | March 1, 2026, 10:03 p.m. |
Created at: March 1, 2026, 7:41 p.m.