Triple
T29341000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Executor |
E744035
|
entity |
| Predicate | featuresGameplayElement |
P92849
|
FINISHED |
| Object | intense combat |
—
|
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: intense combat | Statement: [The Executor, featuresGameplayElement, intense combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresGameplayElement Context triple: [The Executor, featuresGameplayElement, intense combat]
-
A.
featuresGame
Indicates that something (such as a platform, service, or collection) includes or presents a particular game as part of its offerings.
-
B.
gameFeatures
chosen
Indicates that a game includes or offers a particular element, characteristic, or functionality.
-
C.
gameElement
Indicates that one entity functions as a component, feature, or part within the structure or mechanics of a game.
-
D.
gameplayBasis
Indicates that one entity serves as the core mechanic, structure, or inspiration upon which another entity’s gameplay is designed or derived.
-
E.
featuresElementSystem
Indicates that a system includes or incorporates a particular element as one of its constituent parts or components.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: April 28, 2026, 1:33 p.m.