Triple
T37456815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spine Crawler |
E930819
|
entity |
| Predicate | controlledByPlayer |
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: [Spine Crawler, controlledByPlayer, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledByPlayer Context triple: [Spine Crawler, controlledByPlayer, true]
-
A.
isPlayerControlled
chosen
Indicates that an entity is currently being directed or controlled by a human player rather than by the system or AI.
-
B.
controlledByInGame
Indicates that one in-game entity has control or command over another within the context of the game.
-
C.
controllingPlayer
Indicates which player currently has control or authority over a given game element, object, or situation.
-
D.
isRemoteControlled
Indicates that an entity is operated or controlled from a distance via a remote device or system.
-
E.
hasCharacterControl
Indicates that one entity has the ability or authority to direct, manipulate, or govern the behavior or state of another entity.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.