Triple
T11544488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priest |
E273746
|
entity |
| Predicate | winConditionType |
P20842
|
FINISHED |
| Object | value exhaustion of opponent |
—
|
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: value exhaustion of opponent | Statement: [Priest, winConditionType, value exhaustion of opponent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winConditionType Context triple: [Priest, winConditionType, value exhaustion of opponent]
-
A.
conditionOfVictory
chosen
Indicates the specific circumstances or criteria under which a participant is considered to have won.
-
B.
winnerType
Indicates the category or kind of winner associated with an event, competition, or outcome.
-
C.
winnerState
Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
-
D.
gameWinningScoreType
Indicates the type or category of score (e.g., goal, point, run) that results in winning a game.
-
E.
hasWinnerType
Indicates that an entity has a specific type or category of winner associated with it.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e1d754819089f3b6be3404fa0b |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.