Triple
T13459789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mason County, Michigan |
E311328
|
entity |
| Predicate | hasCountyWebsite |
P30293
|
FINISHED |
| Object | https://www.masoncounty.net/ |
—
|
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.masoncounty.net/ | Statement: [Mason County, Michigan, hasCountyWebsite, https://www.masoncounty.net/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyWebsite Context triple: [Mason County, Michigan, hasCountyWebsite, https://www.masoncounty.net/]
-
A.
hasLocalGovernmentWebsite
chosen
Indicates that an entity has an official website specifically for its local government or municipal administration.
-
B.
hasCountyCode
Indicates that an entity is associated with a specific county identified by a standardized county code.
-
C.
includesCounty
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
-
D.
homeCounty
Indicates that a specified county is the primary home or place of residence for a given person or entity.
-
E.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0c177081909178dec61b09c278 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03dcd0c8190a8927eb4eaad1c45 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.