Triple
T17528134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pleasant Lake (water body) |
E426856
|
entity |
| Predicate | hasNearbyCommunityType |
P3292
|
FINISHED |
| Object | communities |
—
|
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: communities | Statement: [Pleasant Lake (water body), hasNearbyCommunityType, communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyCommunityType Context triple: [Pleasant Lake (water body), hasNearbyCommunityType, communities]
-
A.
hasNearbyCommunity
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
B.
hasCommunityType
chosen
Indicates that an entity is associated with or classified under a particular type or category of community.
-
C.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
-
D.
hasNearbyTownType
Indicates that one entity has, in its vicinity, a town of a specified type or classification.
-
E.
hasNearbySiteType
Indicates that one entity has another entity of a specified site type located in its close physical vicinity.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d81a808190ab38831ea5b73b74 |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.