Triple
T21955008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Wallonia |
E542164
|
entity |
| Predicate | heraldicAnimal |
P32838
|
FINISHED |
| Object | rooster |
—
|
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: rooster | Statement: [Coat of arms of Wallonia, heraldicAnimal, rooster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heraldicAnimal Context triple: [Coat of arms of Wallonia, heraldicAnimal, rooster]
-
A.
animalSymbol
Indicates that one entity serves as a symbolic representation or emblem of the other in the form of an animal.
-
B.
heraldicAspect
Indicates a relationship where one entity serves as a heraldic feature, attribute, or component in the coat of arms or heraldic representation of another entity.
-
C.
heraldicCharge
chosen
Indicates that one entity serves as a heraldic charge, i.e., a symbolic figure or emblem placed on another entity’s coat of arms or shield.
-
D.
heraldicConnection
Indicates a relationship where entities are linked through heraldry, such as by shared coats of arms, heraldic symbols, lineage, or official armorial associations.
-
E.
heraldicColor
Indicates that one entity specifies or bears a particular heraldic color in a coat of arms or related heraldic context.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1243f46dc819097e4a1849af7fba4 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:59 p.m.