Triple
T20435013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carle Place, New York, United States |
E501228
|
entity |
| Predicate | residentialCommunity |
P140126
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Carle Place, New York, United States, residentialCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residentialCommunity Context triple: [Carle Place, New York, United States, residentialCommunity, true]
-
A.
isResidentialCommunityOn
Indicates that a residential community is located on or situated along a specified geographic feature, area, or infrastructure.
-
B.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
C.
isPlannedCommunity
Indicates that a community has been intentionally designed and developed according to a coordinated plan rather than growing organically.
-
D.
residentialProfile
Indicates the relationship between an entity and the characteristics or status of where and how it resides or is housed.
-
E.
isResidentialSuburbOf
Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685ee758c8190b267b7ce71de8f8c |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:31 a.m.