Triple
T20767098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denville, New Jersey |
E511124
|
entity |
| Predicate | isLakesRegionCommunity |
P76780
|
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: [Denville, New Jersey, isLakesRegionCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLakesRegionCommunity Context triple: [Denville, New Jersey, isLakesRegionCommunity, true]
-
A.
isLakesideMunicipality
Indicates that a municipality is located on the shore of a lake or directly borders a lake.
-
B.
hasLakeRegion
Indicates that a place or geographic area includes or is associated with a specific lake region.
-
C.
hasNearbyLakeRegion
Indicates that one region is located close to a lake or lake-dominated area.
-
D.
isInlandWaterwayCommunity
Indicates that a community is located along or associated with an inland waterway, such as a river, canal, or lake, rather than on open coastal waters.
-
E.
locatedInLakeRegion
chosen
Indicates that the subject entity is situated within a geographic area characterized as a lake region.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24df58c8190b37398353ce4bf24 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:36 p.m.