Triple
T38643781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Races |
E938666
|
entity |
| Predicate | unlockableBy |
P189627
|
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: [Allied Races, unlockableBy, Alliance players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unlockableBy Context triple: [Allied Races, unlockableBy, Alliance players]
-
A.
unlockableIn
Indicates that one entity can be unlocked, obtained, or made available within the context of another entity (such as a level, mode, or condition).
-
B.
unlockable
Indicates that an entity can be opened or made accessible, typically by using a key, code, or other authorized method.
-
C.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
D.
canUnlock
chosen
Indicates that one entity has the ability or permission to unlock another entity.
-
E.
reachableOnlyBy
Indicates that one entity can be accessed or arrived at exclusively through another specific entity or route, with no alternative paths available.
- 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_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:32 p.m.