Triple
T35257722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Froidchapelle |
E1018278
|
entity |
| Predicate | hasCoatOfArmsImage |
P125931
|
FINISHED |
| Object | Blason ville be Froidchapelle.svg |
—
|
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: Blason ville be Froidchapelle.svg | Statement: [Froidchapelle, hasCoatOfArmsImage, Blason ville be Froidchapelle.svg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoatOfArmsImage Context triple: [Froidchapelle, hasCoatOfArmsImage, Blason ville be Froidchapelle.svg]
-
A.
hasCoatOfArmsFeature
Indicates that an entity’s coat of arms includes or displays a specific feature or element.
-
B.
hasCoatOfArmsDisplay
chosen
Indicates that an entity presents or exhibits a particular coat of arms in a visible or official manner.
-
C.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
D.
coatOfArmsCaption
Indicates the descriptive text that explains or labels the depicted coat of arms.
-
E.
hasNoCoatOfArmsOnStandardVersion
Indicates that the entity’s standard or default version does not display or include a coat of arms.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.