Triple
T17471507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergen Street station |
E425424
|
entity |
| Predicate | upperLevelStatus |
P127577
|
FINISHED |
| Object | in passenger use |
—
|
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: in passenger use | Statement: [Bergen Street station, upperLevelStatus, in passenger use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperLevelStatus Context triple: [Bergen Street station, upperLevelStatus, in passenger use]
-
A.
upperLevels
Indicates that one entity occupies or corresponds to higher levels, tiers, or hierarchical positions relative to another entity.
-
B.
statusLevelAbove
Indicates that one entity’s status level is higher or more advanced than another entity’s status level.
-
C.
upperLevelConnects
Indicates a connection where one entity links to or interfaces with another at a higher or superior level in a hierarchy or structure.
-
D.
hasUpperTier
Indicates that one entity occupies a higher or superior level, rank, or layer in a hierarchical structure relative to another entity.
-
E.
statusLevelBasedOn
Indicates that one entity’s status level is determined or derived from another specified factor or entity.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451abab908190b6d9d8a64f7c2ea3 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:47 a.m.