Triple
T35825412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dux Legnicensis |
E1035627
|
entity |
| Predicate | usedInChancery |
P62953
|
FINISHED |
| Object | ducal chancery of Legnica |
—
|
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: ducal chancery of Legnica | Statement: [Dux Legnicensis, usedInChancery, ducal chancery of Legnica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInChancery Context triple: [Dux Legnicensis, usedInChancery, ducal chancery of Legnica]
-
A.
usedLanguageInChancery
Indicates that a particular language was employed as the official medium of writing and record-keeping in a chancery or administrative office.
-
B.
usedCourt
Indicates that an entity made use of or participated in legal proceedings within a particular court.
-
C.
usedByCourt
Indicates that something (such as a document, argument, or evidence) is utilized or relied upon by a court in its judicial process.
-
D.
hasChancery
chosen
Indicates that an entity possesses or is associated with a chancery, i.e., an official office or administrative body responsible for formal documents and records.
-
E.
usedInCourts
Indicates that something is employed or applied within legal court settings, such as in judicial proceedings or courtroom processes.
- 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
Created at: May 3, 2026, 4:06 p.m.