Triple
T38289571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nesseby |
E1022319
|
entity |
| Predicate | coatOfArmsApprovedBy |
P23467
|
FINISHED |
| Object | King of Norway |
—
|
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: King of Norway | Statement: [Nesseby, coatOfArmsApprovedBy, King of Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coatOfArmsApprovedBy Context triple: [Nesseby, coatOfArmsApprovedBy, King of Norway]
-
A.
coatOfArmsApprovalYear
Indicates the year in which a particular coat of arms was officially approved or granted.
-
B.
replacedOnCoatOfArmsBy
Indicates that one element or symbol on a coat of arms has been superseded and taken the place of by another element or symbol.
-
C.
governingHeraldicAuthority
chosen
Indicates the official heraldic body or authority that has jurisdiction over, regulates, or grants the heraldic item in question.
-
D.
designerOfCoatOfArms
Indicates that one entity is the creator or designer responsible for the coat of arms associated with another entity.
-
E.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.