Triple
T14005769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 18th Avenue (BMT West End Line) |
E336941
|
entity |
| Predicate | hasHelpPointIntercoms |
P5951
|
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: [18th Avenue (BMT West End Line), hasHelpPointIntercoms, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHelpPointIntercoms Context triple: [18th Avenue (BMT West End Line), hasHelpPointIntercoms, yes]
-
A.
hasHelpPoint
Indicates that one entity provides or contains a designated help or assistance point for another entity.
-
B.
hasEmergencyIntercoms
chosen
Indicates that an entity is equipped with emergency intercom devices available for use in urgent or crisis situations.
-
C.
hasCallCenter
Indicates that an entity operates, is associated with, or is served by a call center.
-
D.
callingPoint
Indicates that one entity serves as a stop, station, or intermediate point that another entity (such as a route, journey, or service) calls at or passes through.
-
E.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed327d88190a53af5768468a8eb |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.