Triple
T20619776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Shoes |
E506668
|
entity |
| Predicate | destinationControl |
P114287
|
FINISHED |
| Object | wearer’s wish |
—
|
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: wearer’s wish | Statement: [Silver Shoes, destinationControl, wearer’s wish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destinationControl Context triple: [Silver Shoes, destinationControl, wearer’s wish]
-
A.
controlDirection
chosen
Indicates that one entity exerts influence or guidance over the orientation, course, or movement direction of another entity.
-
B.
directedTo
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
-
C.
transportGoal
Indicates that an entity has the objective or intended outcome of moving or conveying something or someone from one place to another.
-
D.
locationOfControl
Indicates that one entity is the place or context in which another entity exercises authority, management, or control.
-
E.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
- 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6abe0e22c81909f6efe21518e33f0 |
completed | April 20, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.