Triple
T37745784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of Landkreis Freising |
E940839
|
entity |
| Predicate | hasHeraldicFigure |
P71470
|
FINISHED |
| Object | Moor of Freising |
—
|
NE NERFINISHED |
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: Moor of Freising | Statement: [coat of arms of Landkreis Freising, hasHeraldicFigure, Moor of Freising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeraldicFigure Context triple: [coat of arms of Landkreis Freising, hasHeraldicFigure, Moor of Freising]
-
A.
hasHeraldicSubject
chosen
Indicates that one entity serves as the heraldic subject or emblematic figure depicted on another entity, such as on a coat of arms or shield.
-
B.
hasHeraldicMeaning
Indicates that something (typically a symbol, color, or design) carries a specific meaning or significance within the system of heraldry.
-
C.
hasHeraldicRole
Indicates that an entity holds or is assigned a specific role or function within a heraldic context (such as in coats of arms, armorial bearings, or heraldic ceremonies).
-
D.
hasHeraldicUse
Indicates that something is used as, or incorporated into, a heraldic device, emblem, or coat of arms.
-
E.
hasInescutcheon
Indicates that one heraldic shield or coat of arms bears another smaller shield (an inescutcheon) placed upon 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_69f76ee0e32c8190b40a3b4cf590337c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.