Triple
T13482795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blair Township, Michigan |
E318413
|
entity |
| Predicate | hasParentSubdivisionName |
P37103
|
FINISHED |
| Object | Grand Traverse County |
—
|
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: Grand Traverse County | Statement: [Blair Township, Michigan, hasParentSubdivisionName, Grand Traverse County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentSubdivisionName Context triple: [Blair Township, Michigan, hasParentSubdivisionName, Grand Traverse County]
-
A.
hasParentSubdivisionSet
Indicates that an entity is associated with a set of higher-level subdivisions to which it belongs or from which it is derived.
-
B.
hasSubdivisionName3
Indicates that an entity has a third-level subdivision whose name is given by the associated value.
-
C.
hasSubdivisionLabel
Indicates that an entity assigns a specific label or name to one of its subdivisions or component parts.
-
D.
hasStateSubdivisionName
Indicates that an entity has a specific name for one of its internal state-level subdivisions.
-
E.
hasHigherLevelSubdivision
chosen
Indicates that one administrative or organizational unit is contained within and subordinate to a larger, higher-level subdivision.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3868ec8190a6a1803018d4f2d8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.