Triple
T3815762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kok-boru |
E84249
|
entity |
| Predicate | gameElement |
P52035
|
FINISHED |
| Object | scramble for carcass |
—
|
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: scramble for carcass | Statement: [Kok-boru, gameElement, scramble for carcass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameElement Context triple: [Kok-boru, gameElement, scramble for carcass]
-
A.
gameEngine
Indicates that one entity serves as the game engine or core runtime system used to develop, run, or power another entity (such as a game or interactive application).
-
B.
gameContext
Indicates the situational framework or environment in which a game’s actions, rules, and interactions take place.
-
C.
gameLocation
Indicates the place or venue where a game or match takes place.
-
D.
gameState
Indicates the current status or condition of a game at a particular point in time, including relevant rules, progress, and contextual information.
-
E.
game2Location
Indicates that a game takes place at, or is associated with, a specific location.
- F. None of above. chosen
Provenance (4 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7482d708190a3ec74745b102a4c |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:17 p.m.