Triple
T10434823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Lithuania |
E246010
|
entity |
| Predicate | swordPosition |
P93568
|
FINISHED |
| Object | raised |
—
|
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: raised | Statement: [Coat of arms of Lithuania, swordPosition, raised]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: swordPosition Context triple: [Coat of arms of Lithuania, swordPosition, raised]
-
A.
shieldPosition
Indicates the relative location or orientation of a shield with respect to the entity or context it is protecting.
-
B.
ridingPosition
Indicates the relative physical placement or posture of an entity while it is riding or being carried by another entity.
-
C.
positionInArms
Indicates that one entity is being held or carried within the arms of another entity.
-
D.
handPosition
Indicates the spatial location or orientation of a hand relative to a reference point or object.
-
E.
bearerPosition
Indicates the spatial or positional relationship of a bearer (holder or carrier) relative to the item or entity it bears.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea67344c81909984ab99b0ef1e64 |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfbc546881908f312c66ee195f79 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91de3088190ae89cbb12fb29db8 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:14 p.m.