Triple
T34205332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naiman tribe |
E877497
|
entity |
| Predicate | wasRivalOf |
P22658
|
FINISHED |
| Object | Kereit tribe |
—
|
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: Kereit tribe | Statement: [Naiman tribe, wasRivalOf, Kereit tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRivalOf Context triple: [Naiman tribe, wasRivalOf, Kereit tribe]
-
A.
rivalOf
chosen
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
-
B.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
-
C.
bearerRivalOf
Indicates that the bearer is in a state of rivalry or competitive opposition with the related entity.
-
D.
wasEnemyOf
Indicates that one entity regarded or interacted with another as an adversary or opponent, typically in a hostile or conflicting relationship.
-
E.
isPartOfRivalry
Indicates that one entity participates as a member or component in an ongoing rivalry involving another entity.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7104ee44c8190afd450a4a9d3943b |
completed | May 3, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.