Triple
T5735409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flatbush Avenue–Brooklyn College |
E126489
|
entity |
| Predicate | terminalForService |
P24737
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Flatbush Avenue–Brooklyn College, terminalForService, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalForService Context triple: [Flatbush Avenue–Brooklyn College, terminalForService, 2]
-
A.
terminalName
Indicates the name or label assigned to a specific terminal or endpoint within a system or network.
-
B.
servesTerminal
Indicates that one entity functions as a terminal or endpoint facility that is served or operated by another entity.
-
C.
TerminalEUsedFor
Indicates that a terminal E is used for a particular purpose, function, or activity.
-
D.
terminalNumber
chosen
Indicates the specific terminal identifier associated with an entity, such as a device, port, or connection point, within a larger system or network.
-
E.
terminalArea
Indicates that one entity is a designated terminal area or zone associated with another entity (such as a facility, system, or region).
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025596b5c81909b5626773c91cecb |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.