Triple
T35010661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chosen One |
E1009931
|
entity |
| Predicate | playerControlled |
P191462
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chosen One, playerControlled, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerControlled Context triple: [Chosen One, playerControlled, true]
-
A.
playerControl
Indicates that one entity (typically a player) has control or command over another entity or object within a system or environment.
-
B.
isPlayerControlled
chosen
Indicates that an entity is currently being directed or controlled by a human player rather than by the system or AI.
-
C.
secondaryPlayerControls
Indicates that a secondary or supporting player has control or command over another entity or aspect within a system or scenario.
-
D.
isRemoteControlled
Indicates that an entity is operated or controlled from a distance via a remote device or system.
-
E.
playedWhile
Indicates that one activity or event occurred concurrently with another, with the second serving as the temporal context during which the first was performed.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:01 p.m.