Triple
T26428615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulam tribe |
E664438
|
entity |
| Predicate | hasEnemyTribe |
P88397
|
FINISHED |
| Object | Wagabu 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: Wagabu tribe | Statement: [Ulam tribe, hasEnemyTribe, Wagabu tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnemyTribe Context triple: [Ulam tribe, hasEnemyTribe, Wagabu tribe]
-
A.
enemyTribe
chosen
Indicates that one tribe is in an adversarial or hostile relationship with another tribe.
-
B.
hasBrotherTribe
Indicates a relationship where one tribe is recognized as the brother or closely allied counterpart of another tribe.
-
C.
hasNotableTribeAtEncounter
Indicates that, at the time of the encounter, the entity was associated with or identified as belonging to a notable tribe.
-
D.
hasRelatedTribe
Indicates that one tribe is associated or connected to another tribe in some relevant way, such as by kinship, alliance, or shared characteristics.
-
E.
combatantTribe
Indicates a tribal group that participates as a fighter or belligerent party in a conflict or battle.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 26, 2026, 11:47 p.m.