Triple
T38643705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warfronts |
E938664
|
entity |
| Predicate | rotationMechanic |
P142358
|
FINISHED |
| Object | faction control alternates over time |
—
|
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: faction control alternates over time | Statement: [Warfronts, rotationMechanic, faction control alternates over time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationMechanic Context triple: [Warfronts, rotationMechanic, faction control alternates over time]
-
A.
hasRotationMechanic
chosen
Indicates that the subject includes or supports a gameplay or functional mechanic involving rotation or turning as a core interaction.
-
B.
rotationAction
Indicates an action where an entity is turned or rotated around a point, axis, or center by a specified amount or orientation.
-
C.
rotationProcess
Indicates a process in which something is turned or rotated around an axis or point over time.
-
D.
rotationType
Indicates the specific kind or mode of rotational movement or orientation applied in a given context.
-
E.
rotationDrivers
Indicates that one entity causes, controls, or is responsible for the rotation or rotational motion of another entity.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.