Triple
T17517690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PLEX |
E426606
|
entity |
| Predicate | canBeMovedBetween |
P14853
|
FINISHED |
| Object | player characters via in-game trade |
—
|
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: player characters via in-game trade | Statement: [PLEX, canBeMovedBetween, player characters via in-game trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeMovedBetween Context triple: [PLEX, canBeMovedBetween, player characters via in-game trade]
-
A.
canBeReorganizedBy
Indicates that one entity has the ability or authority to rearrange, restructure, or otherwise reorganize another entity.
-
B.
canBeModifiedBetween
Indicates that something is allowed or able to be changed during a specified interval or between defined points or states.
-
C.
canBeShared
chosen
Indicates that something is capable of being distributed or accessed by multiple parties.
-
D.
canBeTransportedOver
Indicates that one entity is capable of being moved or carried across, along, or by means of another entity or medium.
-
E.
canBeReassignedBy
Indicates that one entity has the authority or ability to change or transfer another entity’s assignment or allocation.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452615a8481909974e9855ea7a8e4 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.