Triple
T24787750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cross potent |
E620163
|
entity |
| Predicate | isDepictedInTinctures |
P157127
|
FINISHED |
| Object | metal tinctures |
—
|
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: metal tinctures | Statement: [cross potent, isDepictedInTinctures, metal tinctures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDepictedInTinctures Context triple: [cross potent, isDepictedInTinctures, metal tinctures]
-
A.
colorTincture
Indicates that one entity has a specific heraldic color or tincture applied to it.
-
B.
tinctureOfInscription
Indicates a relationship where an inscription is embodied, preserved, or represented in the form of a tincture or liquid medium.
-
C.
tinctureOfPale
Indicates that one entity is a tincture (medicinal or alcoholic extract) derived from or characterized by the pale aspect, quality, or component of another entity.
-
D.
tinctureRed
Indicates that an entity has a red-colored tincture (heraldic coloring) applied to it.
-
E.
tinctureWhite
Indicates that an entity has the heraldic tincture (color) white or silver as a defining attribute or feature.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4110071008190a430ca780b567fe4 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410a001788190a457e41f53aaf90c |
completed | May 1, 2026, 2:32 a.m. |
Created at: April 18, 2026, 4:46 a.m.