Triple
T28983265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge, Idaho |
E734607
|
entity |
| Predicate | isGatewayCommunity |
P42057
|
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: [Cambridge, Idaho, isGatewayCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGatewayCommunity Context triple: [Cambridge, Idaho, isGatewayCommunity, true]
-
A.
isGatewayCommunityFor
chosen
Indicates that one community serves as an entry point, access hub, or primary connection for another community or larger region.
-
B.
isCommunity
Indicates that an entity functions as or is classified as a community, typically representing a group of individuals connected by shared location, interests, or characteristics.
-
C.
isCommunityBy
Indicates that something functions as or is recognized as a community defined or established by a particular agent or source.
-
D.
isCommunityHub
Indicates that a place or entity functions as a central gathering point or focal location for community activities, services, and interactions.
-
E.
isRemoteCommunity
Indicates that a community is geographically isolated or distant from urban centers and services.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65ee617488190ab8ce4f73be9c651 |
completed | May 2, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:12 a.m.