Triple
T16516089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Alliance |
E401187
|
entity |
| Predicate | gameRuleModifications |
P24476
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Alliance, gameRuleModifications, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameRuleModifications Context triple: [The Alliance, gameRuleModifications, yes]
-
A.
gameEngineModification
Indicates a relationship where an entity alters, extends, or customizes the functionality or behavior of a game engine.
-
B.
typicalRuleModification
chosen
Indicates a change made to a standard or default rule, adjusting how that rule normally applies or operates.
-
C.
affectedByGameRule
Indicates that an entity’s state, behavior, or outcome is influenced or constrained by a specific game rule.
-
D.
notableRuleChange
Indicates a significant modification to an established rule or set of rules that meaningfully alters how they apply or are enforced.
-
E.
gameLengthRule
Indicates a rule that specifies how long a game is allowed or required to last.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7bbfa481909037148cdb4d8996 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.