Triple
T1684768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamaica Center–Parsons/Archer |
E36416
|
entity |
| Predicate | servedByServicePattern |
P1294
|
FINISHED |
| Object | E local in Queens |
—
|
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: E local in Queens | Statement: [Jamaica Center–Parsons/Archer, servedByServicePattern, E local in Queens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByServicePattern Context triple: [Jamaica Center–Parsons/Archer, servedByServicePattern, E local in Queens]
-
A.
servedByService
chosen
Indicates that something is provided, handled, or fulfilled by a particular service.
-
B.
servedByLine
Indicates that a transportation stop, station, or location is provided service by a specific transit line.
-
C.
primaryServicePattern
Indicates the main or most typical way in which a service is delivered, structured, or utilized within a given context.
-
D.
hasServicePatternChange
Indicates that there is a modification in the usual or scheduled pattern of a service’s operation.
-
E.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.