Triple
T10074949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broad Street (BMT Nassau Street Line) |
E213725
|
entity |
| Predicate | isTerminal |
P91950
|
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: [Broad Street (BMT Nassau Street Line), isTerminal, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTerminal Context triple: [Broad Street (BMT Nassau Street Line), isTerminal, yes]
-
A.
hasTerminalFunction
Indicates that something possesses a function or role specifically associated with an endpoint, boundary, or final stage within a system or process.
-
B.
hasTerminalShape
Indicates that one entity possesses or exhibits a particular terminal (end) shape defined by another entity.
-
C.
isMajorTerminalOf
Indicates that one entity serves as a primary or main terminal (such as a key endpoint or hub) for another entity within a system or network.
-
D.
usedTerminal
Indicates that an entity made use of or interacted with a particular terminal or endpoint device.
-
E.
servesTerminal
Indicates that one entity functions as a terminal or endpoint facility that is served or operated by another 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_69ca839add308190b57d53b4ec21f2d0 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd017b8288190a577bd66e4ba66b7 |
completed | April 2, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:59 p.m.