Triple
T38477010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IX |
E915574
|
entity |
| Predicate | hasSpecialEnemyContext |
P199162
|
FINISHED |
| Object | arena champions |
—
|
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: arena champions | Statement: [IX, hasSpecialEnemyContext, arena champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialEnemyContext Context triple: [IX, hasSpecialEnemyContext, arena champions]
-
A.
hasEnemyOccupationContext
Indicates a contextual relationship in which an entity is subject to, or characterized by, control or occupation by an enemy force.
-
B.
hasUniqueEnemy
Indicates that an entity has exactly one distinct enemy with whom it is in an antagonistic relationship.
-
C.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
-
D.
hasSpecialSystem
Indicates that an entity possesses or is equipped with a designated special system or subsystem beyond its standard configuration.
-
E.
hasSpecialUnit
Indicates that an entity possesses or is associated with a distinct, designated unit that has a special role, function, or status.
- F. None of above. chosen
Provenance (4 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69ff234e63648190a7b09a161029c8e2 |
completed | May 9, 2026, 12:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.