Triple
T34905659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German 2 euro commemorative coin (Schleswig-Holstein, 2006) |
E1006718
|
entity |
| Predicate | edgeInscriptionLanguage |
P181847
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [German 2 euro commemorative coin (Schleswig-Holstein, 2006), edgeInscriptionLanguage, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: edgeInscriptionLanguage Context triple: [German 2 euro commemorative coin (Schleswig-Holstein, 2006), edgeInscriptionLanguage, German]
-
A.
inscriptionsLanguage
Indicates that the language used in the inscriptions on an object or surface is the specified language.
-
B.
bellInscriptionLanguage
Indicates the language in which the inscription on a bell is written.
-
C.
mayBeInscribedAs
Indicates that one entity is permitted or suitable to be formally recorded, written, or engraved as another entity.
-
D.
languageOfSignatures
Indicates the language in which the signatures on a document or agreement are written or expressed.
-
E.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
- F. None of above. chosen
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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782cf61948190b98185d961609554 |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782c848fc8190baea8c845ca9079f |
completed | May 3, 2026, 5:15 p.m. |
Created at: May 3, 2026, 4 p.m.