Triple
T13638260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regency Council of the Kingdom of Poland |
E325906
|
entity |
| Predicate | dateOfCivilAuthorityTransfer |
P34797
|
FINISHED |
| Object | 1918-11-14 |
—
|
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: 1918-11-14 | Statement: [Regency Council of the Kingdom of Poland, dateOfCivilAuthorityTransfer, 1918-11-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfCivilAuthorityTransfer Context triple: [Regency Council of the Kingdom of Poland, dateOfCivilAuthorityTransfer, 1918-11-14]
-
A.
dateOfTransferOfPower
chosen
Indicates the specific date on which governing authority or control is formally transferred from one party to another.
-
B.
dateOfSovereigntyTransfer
Indicates the date on which sovereignty or governing authority over an entity was formally transferred from one party to another.
-
C.
deJureTransferDate
Indicates the official legal date on which ownership or rights are formally transferred from one party to another.
-
D.
deFactoTransferDate
Indicates the date on which control or ownership is effectively transferred in practice, regardless of the formal or legal transfer date.
-
E.
administrativeChangeDate
Indicates the date on which an administrative change (such as an update, modification, or reclassification) affecting the entity was officially recorded or took effect.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.