Triple
T6024632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of the Elephant |
E134144
|
entity |
| Predicate | featuresOnCoatOfArms |
P2907
|
FINISHED |
| Object | Danish 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: Danish royal coat of arms | Statement: [Order of the Elephant, featuresOnCoatOfArms, Danish royal coat of arms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresOnCoatOfArms Context triple: [Order of the Elephant, featuresOnCoatOfArms, Danish royal coat of arms]
-
A.
coatOfArmsFeatures
chosen
Indicates that a coat of arms includes or displays specific symbols, colors, or design elements as part of its heraldic composition.
-
B.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
C.
coatOfArmsType
Indicates the specific kind or category of coat of arms associated with an entity.
-
D.
scriptOnCoatOfArms
Indicates that a specific script or writing system appears on, or is inscribed upon, a coat of arms.
-
E.
coatOfArmsCaption
Indicates the descriptive text that explains or labels the depicted coat of arms.
- 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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04fbf048081908b0da0cf838730a5 |
completed | March 22, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:07 p.m.