Triple
T11310458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Malaysia |
E267821
|
entity |
| Predicate | shieldDivisions |
P98443
|
FINISHED |
| Object | five main sections |
—
|
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: five main sections | Statement: [Coat of arms of Malaysia, shieldDivisions, five main sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shieldDivisions Context triple: [Coat of arms of Malaysia, shieldDivisions, five main sections]
-
A.
shieldDivision
Indicates a defensive relationship where one entity protects or buffers another entity or group from harm, impact, or external influence.
-
B.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
C.
shieldDescribedAs
Indicates that a shield is characterized or portrayed using a particular description or set of attributes.
-
D.
shieldPosition
Indicates the relative location or orientation of a shield with respect to the entity or context it is protecting.
-
E.
shieldQuarter
Indicates that one entity is depicted as a quarter (one-fourth) section of a shield in relation to another 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c0b3b88190ac0e3d6a5ad3b9bc |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.