Triple
T25747089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Haute-Vienne |
E648372
|
entity |
| Predicate | imageRepresents |
P97263
|
FINISHED |
| Object | territory of Haute-Vienne |
—
|
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: territory of Haute-Vienne | Statement: [Coat of arms of Haute-Vienne, imageRepresents, territory of Haute-Vienne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imageRepresents Context triple: [Coat of arms of Haute-Vienne, imageRepresents, territory of Haute-Vienne]
-
A.
imageDepictedIn
Indicates that a particular image is shown, represented, or included within another resource or context.
-
B.
imageOf
chosen
Indicates that one entity is a visual representation or depiction of another entity.
-
C.
evokesImageOf
Indicates that one entity triggers or brings to mind a mental image or visual representation of another entity.
-
D.
containsImage
Indicates that one entity includes or embeds an image as part of its content or structure.
-
E.
intendedToDepict
Indicates that one entity was purposefully created or selected in order to visually represent or portray another entity.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd1fb8d88190a03c705fecf22634 |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 3:52 a.m.