Triple
T2312770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palatine lion |
E50995
|
entity |
| Predicate | hasHeraldicAttitude |
P37998
|
FINISHED |
| Object | 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: rampant | Statement: [Palatine lion, hasHeraldicAttitude, rampant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeraldicAttitude Context triple: [Palatine lion, hasHeraldicAttitude, rampant]
-
A.
heraldicCharge
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.
-
B.
hasHeraldicFamily
Indicates that an entity is associated with a particular heraldic family or lineage, typically sharing the same coat of arms or heraldic identity.
-
C.
heraldicTradition
Indicates a relationship where something belongs to, follows, or is characterized by a particular system or style of heraldic customs and practices.
-
D.
governingHeraldicAuthority
Indicates the official heraldic body or authority that has jurisdiction over, regulates, or grants the heraldic item in question.
-
E.
heralds
Indicates that one event, action, or entity serves as a sign or forerunner announcing the imminent arrival or occurrence of another.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc682d094819081a96ffb77c4c42a |
completed | March 7, 2026, 6:32 a.m. |
Created at: March 4, 2026, 7:49 p.m.