Triple
T37176149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villars-Epeney |
E921050
|
entity |
| Predicate | hasCoatOfArmsJurisdiction |
P1663
|
FINISHED |
| Object | canton of Vaud |
E210585
|
NE 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: canton of Vaud | Statement: [Villars-Epeney, hasCoatOfArmsJurisdiction, canton of Vaud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoatOfArmsJurisdiction Context triple: [Villars-Epeney, hasCoatOfArmsJurisdiction, canton of Vaud]
-
A.
hasCoatOfArmsFeature
Indicates that an entity’s coat of arms includes or displays a specific feature or element.
-
B.
hasCoatOfArmsDisplay
Indicates that an entity presents or exhibits a particular coat of arms in a visible or official manner.
-
C.
coatOfArms
chosen
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
D.
hasCoatOfArmsSharedWith
Indicates that two entities share the same coat of arms design or heraldic emblem.
-
E.
usesCoatOfArmsVariant
Indicates that an entity employs an alternative or modified version of a standard coat of arms rather than the primary or original design.
- F. None of above.
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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a406cc118608190ab84c4e35f5ec72e |
completed | June 28, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.