Triple
T9766208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Dormagen |
E236996
|
entity |
| Predicate | diplomaticLanguage |
P90512
|
FINISHED |
| Object | Latin |
—
|
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: Latin | Statement: [Bishopric of Dormagen, diplomaticLanguage, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diplomaticLanguage Context triple: [Bishopric of Dormagen, diplomaticLanguage, Latin]
-
A.
diplomaticSpeechBy
Indicates that a diplomatic speech or formal address is delivered or authored by a particular agent or entity.
-
B.
hasDiplomaticForm
Indicates that an entity maintains a specific type or mode of diplomatic representation or relations.
-
C.
hasDiplomaticFormat
Indicates that a diplomatic communication, document, or interaction follows a specific recognized diplomatic format or protocol.
-
D.
diplomaticPost
Indicates that an entity holds or is assigned to an official diplomatic position or mission representing one state or organization to another.
-
E.
diplomaticPriority
Indicates that one entity is assigned a higher level of importance or urgency in diplomatic relations or negotiations relative to others.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0a15e408190909745cb1c30937d |
completed | April 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:25 p.m.