Triple
T17286560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of the Philippines |
E419668
|
entity |
| Predicate | sinisterHalf |
P126813
|
FINISHED |
| Object | Spanish lion rampant |
—
|
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: Spanish lion rampant | Statement: [Coat of arms of the Philippines, sinisterHalf, Spanish lion rampant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sinisterHalf Context triple: [Coat of arms of the Philippines, sinisterHalf, Spanish lion rampant]
-
A.
sinisterBaseFieldDepicts
Indicates that a base field portrays or visually represents something in a way that is associated with the sinister (left-hand) side in heraldic or symbolic terms.
-
B.
holdsInSinisterPaw
Indicates that an entity is holding another entity in its left (sinister) paw.
-
C.
halves
Indicates that one quantity is exactly half the size, value, or amount of another.
-
D.
hasSupporterSinister
Indicates that an entity has a heraldic supporter positioned on the left (sinister) side of its shield or emblem.
-
E.
side2
Indicates that an entity is positioned on, associated with, or corresponds to the second side of another entity or structure.
- 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.