Triple
T35536528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moldavia |
E1026944
|
entity |
| Predicate | dateOfUnionWithWallachia |
P4318
|
FINISHED |
| Object | 1859 |
—
|
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: 1859 | Statement: [Moldavia, dateOfUnionWithWallachia, 1859]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfUnionWithWallachia Context triple: [Moldavia, dateOfUnionWithWallachia, 1859]
-
A.
dateOfUnionFormation
Indicates the date on which a union was formally established or came into existence.
-
B.
unificationDate
chosen
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
C.
dateOfPrussianHomage
Indicates the specific date on which the Prussian Homage event took place or was formally recorded.
-
D.
successorInWallachia
Indicates that one entity directly follows another in a succession line specific to Wallachia, such as in rulership or office.
-
E.
predecessorInWallachia
Indicates that one entity held a given position or role in Wallachia immediately before the other entity.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:04 p.m.