Triple
T32412529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanenstenhawi |
E828262
|
entity |
| Predicate | wasAdoptedInto |
P143128
|
FINISHED |
| Object | Mohawk society |
—
|
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: Mohawk society | Statement: [Kanenstenhawi, wasAdoptedInto, Mohawk society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAdoptedInto Context triple: [Kanenstenhawi, wasAdoptedInto, Mohawk society]
-
A.
saidToHaveBeenAdoptedBy
Indicates that one entity is reported or believed to have been adopted by another entity, without asserting it as an established fact.
-
B.
adoptedUnder
Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
-
C.
adoptedInto
chosen
Indicates that one entity has been taken in and legally or formally accepted as a member of another entity’s family, group, or organization.
-
D.
adoptedThrough
Indicates that an adoption relationship was established or carried out by means of a specified process, channel, or intermediary.
-
E.
givenInAdoptionBy
Indicates that an entity was transferred into adoption through the action or decision of a specific giver (such as a person or organization).
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2574a288190b39da76887444b3b |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:53 a.m.