Triple
T35808659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Apex Predator |
E1035168
|
entity |
| Predicate | associatedWithFeudStyle |
P119353
|
FINISHED |
| Object | vicious grudge rivalries |
—
|
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: vicious grudge rivalries | Statement: [The Apex Predator, associatedWithFeudStyle, vicious grudge rivalries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFeudStyle Context triple: [The Apex Predator, associatedWithFeudStyle, vicious grudge rivalries]
-
A.
feudedWith
Indicates a prolonged, often hostile conflict or rivalry between two entities.
-
B.
hadFeudatory
Indicates that one entity served as a subordinate or vassal state under the authority or suzerainty of another entity.
-
C.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
-
D.
feudType
chosen
Indicates the specific kind or category of ongoing conflict or long-standing hostility that exists between entities.
-
E.
inspiredFeudWith
Indicates that one entity’s actions, ideas, or influence sparked or provoked a feud or ongoing conflict with 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.