Triple
T13039177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Grenada |
E326643
|
entity |
| Predicate | featuresOnShield |
P108401
|
FINISHED |
| Object | golden cross |
—
|
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: golden cross | Statement: [Coat of arms of Grenada, featuresOnShield, golden cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresOnShield Context triple: [Coat of arms of Grenada, featuresOnShield, golden cross]
-
A.
featuresShield
Indicates that an entity includes or is equipped with a shield as one of its characteristics or components.
-
B.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
C.
shieldPresent
Indicates that a protective shield is currently active or available in the given context.
-
D.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
E.
securityFeature
Indicates that an entity provides, embodies, or is associated with a mechanism or property intended to enhance safety, protection, or defense against threats or vulnerabilities.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
| PDg | Predicate description generation | batch_69d98a9577d081908ddef9ea77e408e2 |
completed | April 10, 2026, 11:41 p.m. |
Created at: April 9, 2026, 8:55 p.m.