Triple
T9075481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sceptre with the Dove |
E217472
|
entity |
| Predicate | carriedInRightOrLeftHand |
P87059
|
FINISHED |
| Object | left hand of the monarch |
—
|
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: left hand of the monarch | Statement: [Sceptre with the Dove, carriedInRightOrLeftHand, left hand of the monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedInRightOrLeftHand Context triple: [Sceptre with the Dove, carriedInRightOrLeftHand, left hand of the monarch]
-
A.
battingHand
Indicates the handedness a player uses when batting, such as right-handed, left-handed, or switch.
-
B.
handedness
Indicates the preference or dominance of one hand over the other in performing actions or tasks.
-
C.
rightHandedComponent
Indicates that one entity functions as the right-handed component or counterpart within a paired or bilateral relationship to another entity.
-
D.
ambidextrousUse
Indicates the ability to use both the left and right hands with equal skill or effectiveness for a given action or task.
-
E.
handPosition
Indicates the spatial location or orientation of a hand relative to a reference point or object.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc95c53274819099b3b3047bfe8cc8 |
completed | April 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:12 p.m.