Triple
T36028640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tito Ortiz |
E1042197
|
entity |
| Predicate | foughtRival |
P109978
|
FINISHED |
| Object | Ken Shamrock |
—
|
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: Ken Shamrock | Statement: [Tito Ortiz, foughtRival, Ken Shamrock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foughtRival Context triple: [Tito Ortiz, foughtRival, Ken Shamrock]
-
A.
rivalryCharacterizedBy
Indicates a relationship where a rivalry is defined or distinguished by a particular feature, quality, or circumstance.
-
B.
feudedWith
chosen
Indicates a prolonged, often hostile conflict or rivalry between two entities.
-
C.
hadPrimaryRivalry
Indicates that one entity was the main or most significant rival of another entity.
-
D.
facedOpponent
Indicates that one entity directly confronted or competed against another as an opponent in a contest, conflict, or challenge.
-
E.
involvesRivalryBetween
Indicates a relationship in which two or more entities are engaged in rivalry or competitive opposition with one another.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ad15f3b88190b7c9742a734fec5f |
completed | May 3, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.