Triple
T34022725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Melbourne’s government |
E872424
|
entity |
| Predicate | startTimeFirstMinistry |
P20266
|
FINISHED |
| Object | 16 July 1834 |
—
|
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: 16 July 1834 | Statement: [Lord Melbourne’s government, startTimeFirstMinistry, 16 July 1834]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeFirstMinistry Context triple: [Lord Melbourne’s government, startTimeFirstMinistry, 16 July 1834]
-
A.
termAsMinisterStart
Indicates the date or point in time when an individual begins serving in a specific ministerial position.
-
B.
endTimeFirstTermAsPrimeMinister
Indicates the date and time when an individual’s first term serving as prime minister comes to an end.
-
C.
termStartAsMinisterGeneral
Indicates the date or point in time when an individual begins serving in the role of Minister General.
-
D.
firstPrimeMinisterTermStart
chosen
Indicates the date on which an entity began serving its first term as prime minister.
-
E.
termStartAsChancellor
Indicates the date or point in time when an individual begins their term serving in the role of chancellor.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fffc783b648190bcd7df017514d206 |
completed | May 10, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69fffc03fa24819099e12413dc6e0afd |
completed | May 10, 2026, 3:31 a.m. |
Created at: May 1, 2026, 1:51 a.m.