Triple
T38593393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caduceus Blaster |
E932504
|
entity |
| Predicate | isPlayerControlled |
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: [Caduceus Blaster, isPlayerControlled, True]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlayerControlled Context triple: [Caduceus Blaster, isPlayerControlled, True]
-
A.
isRemoteControlled
Indicates that an entity is operated or controlled from a distance via a remote device or system.
-
B.
hasCharacterControl
Indicates that one entity has the ability or authority to direct, manipulate, or govern the behavior or state of another entity.
-
C.
isManualPlayable
Indicates that something can be performed or operated manually by a person, rather than automatically or by a system.
-
D.
hasPhysicalControl
Indicates that one entity currently exercises direct, tangible control or possession over another entity or object.
-
E.
canBeControlledFrom
Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
- F. None of above. chosen
Provenance (4 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:32 p.m.