Triple
T10601240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeeland, Michigan |
E275750
|
entity |
| Predicate | commonAncestryGroup |
P17402
|
FINISHED |
| Object | Dutch ancestry |
—
|
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: Dutch ancestry | Statement: [Zeeland, Michigan, commonAncestryGroup, Dutch ancestry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonAncestryGroup Context triple: [Zeeland, Michigan, commonAncestryGroup, Dutch ancestry]
-
A.
hasCommonAncestryGroup
chosen
Indicates that the related entities share membership in the same ancestral or lineage-based group.
-
B.
sharesCommonAncestorWith
Indicates that two entities have at least one ancestor in common in their lineage or hierarchy.
-
C.
ancestralGroup
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
-
D.
includesCommonGroups
Indicates that two entities share at least one group or category in common.
-
E.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4992248190b640d743ccf02c82 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:31 p.m.