Triple
T25900051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sauk Village, Illinois |
E652585
|
entity |
| Predicate | hasLocalWebsite |
P30293
|
FINISHED |
| Object | https://www.saukvillage.org/ |
—
|
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: https://www.saukvillage.org/ | Statement: [Sauk Village, Illinois, hasLocalWebsite, https://www.saukvillage.org/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalWebsite Context triple: [Sauk Village, Illinois, hasLocalWebsite, https://www.saukvillage.org/]
-
A.
hasCampaignWebsite
Indicates that an entity (typically a political candidate or campaign) is associated with a specific official campaign website.
-
B.
hasLocalGovernmentWebsite
chosen
Indicates that an entity has an official website specifically for its local government or municipal administration.
-
C.
hasMainSite
Indicates that one entity is designated as the primary or central site associated with another entity.
-
D.
hasCompanionWebsite
Indicates that something is associated with or supported by a dedicated companion website.
-
E.
hasTourismWebsite
Indicates that an entity has an associated official website specifically dedicated to providing tourism-related information about it.
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 22, 2026, 8:24 a.m.