Triple
T32412532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanenstenhawi |
E828262
|
entity |
| Predicate | maintainedTiesWith |
P26922
|
FINISHED |
| Object | Mohawk kin |
—
|
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 kin | Statement: [Kanenstenhawi, maintainedTiesWith, Mohawk kin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedTiesWith Context triple: [Kanenstenhawi, maintainedTiesWith, Mohawk kin]
-
A.
hasSocialTieWith
Indicates a social relationship or connection exists between two entities, such as friendship, acquaintance, or other interpersonal tie.
-
B.
maintainsTieWith
chosen
Indicates that one entity keeps an ongoing connection or relationship with another entity over time.
-
C.
hasStrongTiesTo
Indicates a close, influential, and enduring relationship or connection exists between the referenced entities.
-
D.
claimsToHaveBrokenTiesWith
Indicates that one entity asserts it has ended or severed its relationship or association with another entity.
-
E.
maintainsTransnationalTies
Indicates that an entity sustains ongoing social, economic, political, or cultural connections that span across national borders.
- 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_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 12:53 a.m.