Triple
T9564883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planetary Union |
E230764
|
entity |
| Predicate | hasAdversary |
P68850
|
FINISHED |
| Object | Krill |
—
|
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: Krill | Statement: [Planetary Union, hasAdversary, Krill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdversary Context triple: [Planetary Union, hasAdversary, Krill]
-
A.
hasMainAdversary
chosen
Indicates that an entity’s primary or most significant opponent, rival, or enemy is another specified entity.
-
B.
hasOpposingAgent
Indicates that an entity is opposed or counteracted by another agent in a given context or interaction.
-
C.
hasOpposingSide
Indicates that one entity possesses or is associated with another entity that lies on the opposite or facing side relative to a reference orientation or boundary.
-
D.
portraysAdversary
Indicates that one entity depicts or represents another entity as an opponent, enemy, or rival.
-
E.
primaryAdversaryImplied
Indicates that an entity is understood or suggested, rather than explicitly stated, to be the main opponent or chief adversary of 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd996a01b081908e2782f41520f73d |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:04 p.m.