Triple
T32856984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craryville |
E840401
|
entity |
| Predicate | hasCommunityWithin |
P205183
|
FINISHED |
| Object | town of Copake |
E213757
|
NE 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: town of Copake | Statement: [Craryville, hasCommunityWithin, town of Copake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityWithin Context triple: [Craryville, hasCommunityWithin, town of Copake]
-
A.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
B.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
-
C.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
-
D.
hasTargetCommunity
Indicates that something is specifically intended for, directed toward, or designed to serve a particular community or group.
-
E.
hasSubcommunityIn
Indicates that a larger community contains or encompasses a smaller, distinct subcommunity located within it.
- F. None of above. chosen
Provenance (5 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34e4f56a58819085a4a6f6723cb826 |
completed | June 19, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:17 a.m.