Triple
T29655425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Templar Archives |
E750249
|
entity |
| Predicate | supportsPlaystyle |
P192035
|
FINISHED |
| Object | psionic-based army compositions |
—
|
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: psionic-based army compositions | Statement: [Templar Archives, supportsPlaystyle, psionic-based army compositions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPlaystyle Context triple: [Templar Archives, supportsPlaystyle, psionic-based army compositions]
-
A.
supportsGameStyle
chosen
Indicates that one entity is compatible with or able to accommodate a particular game style or mode of play.
-
B.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
C.
playstyleBenefit
Indicates that one playstyle provides an advantage, improvement, or positive effect to a player or entity.
-
D.
supportsPlayers
Indicates that an entity provides compatibility or functionality for one or more players to participate or be used.
-
E.
associatedWithStyleOfPlayOfBearer
Indicates that something is connected to or characterized by the style of play exhibited by the bearer.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 6:54 p.m.