Triple
T2796894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quake franchise |
E53056
|
entity |
| Predicate | competitiveMode |
P15224
|
FINISHED |
| Object | duel |
—
|
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: duel | Statement: [Quake franchise, competitiveMode, duel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitiveMode Context triple: [Quake franchise, competitiveMode, duel]
-
A.
competitiveGame
chosen
Indicates a relationship where entities participate in a game or contest in which they compete against each other to win or achieve a higher ranking.
-
B.
competitiveEffect
Indicates that one entity’s actions or presence influence another entity’s ability to compete, typically by enhancing or diminishing its competitive position or performance.
-
C.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
D.
competition
Indicates a relationship where two or more entities strive against each other to achieve a superior outcome, advantage, or reward.
-
E.
competitiveStatus
Indicates the nature or level of competition that exists between entities, such as whether they are rivals, collaborators, or non-competitors.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddf0f4988190bffc3abab7edbb81 |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.