Triple
T34731795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagome iudex |
E1001231
|
entity |
| Predicate | recordsDonationOf |
P195010
|
FINISHED |
| Object | Mieszko I’s realm |
—
|
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: Mieszko I’s realm | Statement: [Dagome iudex, recordsDonationOf, Mieszko I’s realm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsDonationOf Context triple: [Dagome iudex, recordsDonationOf, Mieszko I’s realm]
-
A.
archiveDonatedTo
Indicates that an archive has been given or transferred as a donation to a recipient institution or entity.
-
B.
donatedWith
Indicates that an entity made a donation using, accompanied by, or in association with a particular method, item, or context.
-
C.
donates
Indicates the act of voluntarily giving something of value, such as money, goods, or time, from one entity to another without expecting payment in return.
-
D.
donated
Indicates that one entity voluntarily gave something of value (such as money, goods, or time) to another entity, typically without expecting anything in return.
-
E.
donationResultedIn
Indicates that a donation directly caused or brought about a particular outcome or consequence.
- 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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: May 3, 2026, 3:59 p.m.