Triple
T34022727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Melbourne’s government |
E872424
|
entity |
| Predicate | startTimeSecondMinistry |
P129995
|
FINISHED |
| Object | 18 April 1835 |
—
|
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: 18 April 1835 | Statement: [Lord Melbourne’s government, startTimeSecondMinistry, 18 April 1835]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeSecondMinistry Context triple: [Lord Melbourne’s government, startTimeSecondMinistry, 18 April 1835]
-
A.
endTimeSecondMinistry
Indicates the second (0–59) component of the time at which a ministry-related event or period ends.
-
B.
startTime (Minister of Justice)
Indicates the point in time at which an individual begins serving as Minister of Justice.
-
C.
startTime (Minister to the UK)
Indicates the date and time at which the person began serving in the role of Minister to the UK.
-
D.
termStartAsMinisterGeneral
Indicates the date or point in time when an individual begins serving in the role of Minister General.
-
E.
termStartOfSecondGovernment
chosen
Indicates that a given time or event marks the beginning of the second term of a particular government.
- 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_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
Created at: May 1, 2026, 1:51 a.m.