Triple
T275135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dieu et mon droit |
E5229
|
entity |
| Predicate | positionOnArms |
P5132
|
FINISHED |
| Object | placed below the shield on the royal coat of arms |
—
|
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: placed below the shield on the royal coat of arms | Statement: [Dieu et mon droit, positionOnArms, placed below the shield on the royal coat of arms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnArms Context triple: [Dieu et mon droit, positionOnArms, placed below the shield on the royal coat of arms]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
C.
positionB
chosen
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
D.
appliesToPosition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific position or role.
-
E.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25dd1cdf881909c2c9b77b7f88684 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b7345c4819086c21710864a1b42 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.