Triple
T12631476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wyandot of Anderdon Nation |
E301650
|
entity |
| Predicate | peoplehoodBasis |
P65880
|
FINISHED |
| Object | common 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: common ancestry | Statement: [Wyandot of Anderdon Nation, peoplehoodBasis, common ancestry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peoplehoodBasis Context triple: [Wyandot of Anderdon Nation, peoplehoodBasis, common ancestry]
-
A.
peoplehood
chosen
Indicates a relationship in which individuals share a common collective identity, culture, or heritage that binds them together as a distinct people.
-
B.
regionOfHabitation
Indicates the geographic area or environment in which an entity typically lives or resides.
-
C.
traditionalPeople
Indicates that the subject consists of or is associated with people who maintain long-established customs, beliefs, or ways of life.
-
D.
habitation
Indicates that one entity serves as the dwelling place, residence, or living environment for another entity.
-
E.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:15 p.m.