Triple
T21666059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Denmark |
E534718
|
entity |
| Predicate | heartArrangement |
P145369
|
FINISHED |
| Object | scattered between lions |
—
|
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: scattered between lions | Statement: [Coat of arms of Denmark, heartArrangement, scattered between lions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heartArrangement Context triple: [Coat of arms of Denmark, heartArrangement, scattered between lions]
-
A.
heartStructure
Indicates that one entity is a structural component, region, or anatomical feature of the heart of another entity.
-
B.
heartSymbol2
Indicates a relationship where one entity expresses affection, love, or strong positive emotion toward another, often symbolized by a heart icon or shape.
-
C.
heartColor
Indicates the color attribute associated with a heart.
-
D.
heartShape
Indicates that one entity has a heart-like or heart-shaped form in relation to another entity or context.
-
E.
heartPresence
Indicates the existence or presence of a heart in or associated with the referenced entity.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c0c236881909ffaefea8601b1c2 |
completed | April 27, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:36 p.m.