Triple
T2378610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of New Zealand |
E46258
|
entity |
| Predicate | shieldCharge |
P10236
|
FINISHED |
| Object | four stars of the Southern 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: four stars of the Southern Cross | Statement: [Coat of arms of New Zealand, shieldCharge, four stars of the Southern Cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shieldCharge Context triple: [Coat of arms of New Zealand, shieldCharge, four stars of the Southern Cross]
-
A.
shieldPosition
Indicates the relative location or orientation of a shield with respect to the entity or context it is protecting.
-
B.
shieldDivision
Indicates a defensive relationship where one entity protects or buffers another entity or group from harm, impact, or external influence.
-
C.
shieldColor
Indicates the color attribute assigned to a shield in the relationship.
-
D.
shieldDepicts
chosen
Indicates that a shield bears or displays a particular image, symbol, or design as its depiction.
-
E.
shieldTincture
Indicates the heraldic color, pattern, or material applied to the surface of a shield.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7974aa481908799ef2f854d1c9d |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.