Triple
T1782741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brill streetcar |
E39323
|
entity |
| Predicate | passengerAccess |
P32331
|
FINISHED |
| Object | low steps from street level |
—
|
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: low steps from street level | Statement: [Brill streetcar, passengerAccess, low steps from street level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerAccess Context triple: [Brill streetcar, passengerAccess, low steps from street level]
-
A.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
B.
passengerCount
Indicates the number of passengers associated with a given entity, such as a vehicle or trip.
-
C.
passengers
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
D.
hasPassengerRole
Indicates that an entity participates in a context or event specifically in the capacity or role of a passenger.
-
E.
hasPassengerHandling
Indicates that an entity is responsible for or involved in managing the processes and services related to handling passengers.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab74db3dbc8190ab256a4e158062b8 |
completed | March 7, 2026, 12:44 a.m. |
Created at: March 4, 2026, 7:31 p.m.