Triple
T36417987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Census Bureau Wisconsin region |
E897065
|
entity |
| Predicate | usesAsBoundary |
P91946
|
FINISHED |
| Object | State of Wisconsin |
—
|
NE NERFINISHED |
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: State of Wisconsin | Statement: [United States Census Bureau Wisconsin region, usesAsBoundary, State of Wisconsin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAsBoundary Context triple: [United States Census Bureau Wisconsin region, usesAsBoundary, State of Wisconsin]
-
A.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
B.
isPartOfLargerBoundary
Indicates that one boundary is contained within or forms a component of a larger encompassing boundary.
-
C.
usedAsBorder
chosen
Indicates that one entity functions as a boundary or dividing line for another entity.
-
D.
hasBoundaryUnit
Indicates that one entity uses or is associated with a specific unit of measurement for its boundary or limit.
-
E.
boundaryMayInclude
Indicates that the boundary of one entity can optionally contain or encompass another entity.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.