Triple
T38587048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwarven District |
E932367
|
entity |
| Predicate | playableFactionAccess |
P189507
|
FINISHED |
| Object | Alliance players |
—
|
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: Alliance players | Statement: [Dwarven District, playableFactionAccess, Alliance players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableFactionAccess Context triple: [Dwarven District, playableFactionAccess, Alliance players]
-
A.
featuresPlayableFaction
Indicates that a game or scenario includes a faction that players can actively control or play as.
-
B.
gameFaction
Indicates that an entity belongs to, is aligned with, or is a member of a particular faction within a game.
-
C.
availableToFaction
chosen
Indicates that something can be accessed, used, or obtained by a particular faction.
-
D.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
E.
isPlayableAllyOf
Indicates that one entity can be used or controlled as an ally in conjunction with another entity, typically within a game or interactive context.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:32 p.m.