Triple
T1485022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arms of France |
E29445
|
entity |
| Predicate | tinctureOfCharge |
P24010
|
FINISHED |
| Object | or |
—
|
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: or | Statement: [arms of France, tinctureOfCharge, or]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tinctureOfCharge Context triple: [arms of France, tinctureOfCharge, or]
-
A.
chargeTincture
chosen
Indicates that a heraldic charge bears a specific tincture (color, metal, or fur) in a coat of arms.
-
B.
tressureTincture
Indicates the color or pattern (tincture) applied specifically to a tressure in heraldic design.
-
C.
tinctureOfLion
Indicates a relationship where something is a medicinal or alchemical preparation (a “tincture”) derived from or associated with a lion.
-
D.
chiefTincture
Indicates that one entity serves as the primary or dominant coloring or tonal quality in relation to another entity.
-
E.
tinctureOfField
Indicates that one entity is a tincture (medicinal extract or solution) derived from, based on, or primarily composed of another entity representing a field or source material.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6a011f0819086e9ee517ed6d29f |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.