Triple
T8141996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archer Avenue Lines |
E190118
|
entity |
| Predicate | isKeyTransitCorridorFor |
P58953
|
FINISHED |
| Object | southeastern 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: southeastern Queens | Statement: [Archer Avenue Lines, isKeyTransitCorridorFor, southeastern Queens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyTransitCorridorFor Context triple: [Archer Avenue Lines, isKeyTransitCorridorFor, southeastern Queens]
-
A.
formsTransportCorridorBetween
Indicates that something creates or constitutes a transportation link or route connecting two locations or entities.
-
B.
transportCorridor
Indicates a route or pathway used to move people, goods, or resources between locations.
-
C.
partOfTransportCorridorTo
chosen
Indicates that one entity forms a component or segment of a larger transport corridor leading to another entity.
-
D.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
E.
isTransportHubBetween
Indicates that a location functions as a central node facilitating transportation connections between two or more other places.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4443a3748190bbae79f1d673c03d |
completed | March 31, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:36 p.m.