Triple
T17286558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of the Philippines |
E419668
|
entity |
| Predicate | shieldPartition |
P126812
|
FINISHED |
| Object | per pale |
—
|
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: per pale | Statement: [Coat of arms of the Philippines, shieldPartition, per pale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shieldPartition Context triple: [Coat of arms of the Philippines, shieldPartition, per pale]
-
A.
shieldDivision
Indicates a defensive relationship where one entity protects or buffers another entity or group from harm, impact, or external influence.
-
B.
shieldDivisions
Indicates that one entity provides protective separation or buffering between different parts, groups, or segments of another entity.
-
C.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
D.
shieldPosition
Indicates the relative location or orientation of a shield with respect to the entity or context it is protecting.
-
E.
shieldDescribedAs
Indicates that a shield is characterized or portrayed using a particular description or set of attributes.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4378024988190aac6aec006f8f7a1 |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:40 a.m.