Triple
T24684692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexington Avenue–Eastern Parkway corridor |
E611248
|
entity |
| Predicate | followsParkway |
P56524
|
FINISHED |
| Object | Eastern Parkway |
—
|
NE NERFINISHED |
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: Eastern Parkway | Statement: [Lexington Avenue–Eastern Parkway corridor, followsParkway, Eastern Parkway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsParkway Context triple: [Lexington Avenue–Eastern Parkway corridor, followsParkway, Eastern Parkway]
-
A.
followsTour
Indicates that one entity attends or participates in a tour that occurs after, or as a consequence of, another specified event or tour.
-
B.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
C.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
D.
followsHighway
chosen
Indicates that one entity’s path or route runs along, parallels, or adheres closely to the course of a specified highway.
-
E.
partOfChainOfParks
Indicates that an entity is one segment or component within a connected sequence of parks or green spaces.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:17 a.m.