Triple
T19012805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of London coat of arms |
E465269
|
entity |
| Predicate | hasCrossTincture |
P93571
|
FINISHED |
| Object | gules |
—
|
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: gules | Statement: [City of London coat of arms, hasCrossTincture, gules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrossTincture Context triple: [City of London coat of arms, hasCrossTincture, gules]
-
A.
crossTincture
chosen
Indicates that one entity bears or displays a cross whose tincture (heraldic color or pattern) is specified or characterized in relation to another entity.
-
B.
fieldForCrossTincture
Indicates that a field (background area) is designated to receive a cross tincture (coloring or pattern) in a heraldic design.
-
C.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
D.
hasCrossColor
Indicates that an entity possesses a cross-shaped marking or pattern of a specified color.
-
E.
crossedWith
Indicates that one entity has moved from one side of another entity or boundary to the opposite side, typically by passing over or through it.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6a9bac8819093f9af57000667b0 |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.