Triple
T38172551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glenwood Landing, New York |
E1000114
|
entity |
| Predicate | nearestIncorporatedVillage |
P190746
|
FINISHED |
| Object | Sea Cliff, New York |
—
|
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: Sea Cliff, New York | Statement: [Glenwood Landing, New York, nearestIncorporatedVillage, Sea Cliff, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestIncorporatedVillage Context triple: [Glenwood Landing, New York, nearestIncorporatedVillage, Sea Cliff, New York]
-
A.
nearestTownDistance
Indicates the distance from a given location to the closest town.
-
B.
hasNearestLargerSettlement
Indicates that one settlement is associated with the geographically closest settlement that is larger in size or population.
-
C.
nearestTownCenter
Indicates that one location is the closest town center to another specified point or area.
-
D.
hasNearbyTraditionalVillage
Indicates that an entity is located close to or in the vicinity of a traditional village.
-
E.
nearestInhabitedTerritory
Indicates that one territory is the closest inhabited territory to another specified location or territory.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: May 3, 2026, 4:29 p.m.