Triple
T5979828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the Archbishop of York |
E133090
|
entity |
| Predicate | tinctureOfCross |
P67841
|
FINISHED |
| Object | argent |
—
|
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: argent | Statement: [Arms of the Archbishop of York, tinctureOfCross, argent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tinctureOfCross Context triple: [Arms of the Archbishop of York, tinctureOfCross, argent]
-
A.
tinctureOfLion
Indicates a relationship where something is a medicinal or alchemical preparation (a “tincture”) derived from or associated with a lion.
-
B.
tressureTincture
Indicates the color or pattern (tincture) applied specifically to a tressure in heraldic design.
-
C.
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.
-
D.
tinctureOfAxe
Indicates that one entity is a tincture (medicinal or extract preparation) derived from or associated with an axe.
-
E.
crownTincture
Indicates the heraldic color or pattern applied to a crown in a coat of arms.
- 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_69c0086f45e8819098f73dd16d45ec9d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc2243c8190bd3488e7b24af985 |
completed | March 22, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c049dcb3c081908ccc9b4d4b210229 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04dbefd1081909795fe1a812b991a |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 4:04 p.m.