Triple
T36454572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 116th Street (planned) |
E898115
|
entity |
| Predicate | hasPlannedLocale |
P195617
|
FINISHED |
| Object | East Harlem, Manhattan |
—
|
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: East Harlem, Manhattan | Statement: [116th Street (planned), hasPlannedLocale, East Harlem, Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedLocale Context triple: [116th Street (planned), hasPlannedLocale, East Harlem, Manhattan]
-
A.
hasMainLocale
Indicates that an entity’s primary or default locale (language and regional setting) is a specified locale.
-
B.
hasLocaleName
Indicates that an entity has a specific name or label used in a particular language or regional locale.
-
C.
hasPlannedPart
Indicates that one entity includes another entity as a component or segment within a planned or scheduled whole.
-
D.
hasGlobalPlan
Indicates that an entity possesses or is associated with an overarching, comprehensive plan that applies at a global or system-wide level.
-
E.
hasPlannedDistrict
Indicates that an entity is associated with or contains a district that has been formally planned or designated according to an organized development scheme.
- F. None of above. chosen
Provenance (4 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69fddac42c4081908568649058e86458 |
completed | May 8, 2026, 12:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.