Triple
T1018039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Arms of England and Scotland quarterly |
E21975
|
entity |
| Predicate | typicalCrestPlacement |
P13359
|
FINISHED |
| Object | above the shield |
—
|
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: above the shield | Statement: [Royal Arms of England and Scotland quarterly, typicalCrestPlacement, above the shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCrestPlacement Context triple: [Royal Arms of England and Scotland quarterly, typicalCrestPlacement, above the shield]
-
A.
crest
Indicates reaching the highest point or peak of something, such as a wave, hill, or trend, before it begins to decline.
-
B.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
C.
ridgeType
Indicates the specific morphological or structural category that a ridge belongs to within a classification of ridge forms.
-
D.
locatedAtBaseOf
Indicates that one entity is positioned at or near the bottom or lowest supporting part of another entity.
-
E.
sitsAtop
chosen
Indicates that one entity is positioned directly on top of another, typically resting upon its upper surface.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c4d488819081d8214ba0a22fe5 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.