Triple
T36804839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of Montfort-l’Amaury |
E909418
|
entity |
| Predicate | armedTincture |
P186316
|
FINISHED |
| Object | azure |
—
|
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: azure | Statement: [Arms of Montfort-l’Amaury, armedTincture, azure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedTincture Context triple: [Arms of Montfort-l’Amaury, armedTincture, azure]
-
A.
axeBladeTincture
Indicates that the blade of an axe is assigned a specific heraldic tincture (color or pattern).
-
B.
typicalTincture
Indicates that something has the usual or standard tincture (coloring or hue) typically associated with it.
-
C.
fieldTincture
Indicates the heraldic tincture (color, metal, or fur) applied to the main background field of a coat of arms.
-
D.
tinctureOfKey
Indicates that one entity is a tincture (medicinal or alcoholic extract) derived from, containing, or primarily based on another entity designated as the key ingredient.
-
E.
tinctureOfMace
Indicates that an entity is a medicinal or flavoring preparation made by extracting the active components of mace (the spice) into a solvent, typically alcohol.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabdd2d88190be1c8de7e499cb83 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7ca91f1808190b2a05c4b691da0bb |
completed | May 3, 2026, 10:22 p.m. |
Created at: May 3, 2026, 4:12 p.m.