Triple
T29050911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contest of Champions arena |
E735258
|
entity |
| Predicate | selectionMethodForCombatants |
P96636
|
FINISHED |
| Object | forced conscription |
—
|
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: forced conscription | Statement: [Contest of Champions arena, selectionMethodForCombatants, forced conscription]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionMethodForCombatants Context triple: [Contest of Champions arena, selectionMethodForCombatants, forced conscription]
-
A.
delegateSelectionMethod
Indicates the method or process by which responsibility or authority is assigned from one entity to another.
-
B.
winnerSelectionMethod
Indicates the process or criteria used to determine which participant is chosen as the winner.
-
C.
methodOfCombat
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
-
D.
selectionRitual
chosen
Indicates a process or ceremony through which one or more entities are chosen from a set of candidates.
-
E.
gameSelectionMethod
Indicates the method or criteria used to choose or determine which game is selected among available options.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 10:08 a.m.