Triple
T11954834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ed Balls |
E284523
|
entity |
| Predicate | shadowOfficeStart |
P1383
|
FINISHED |
| Object | 2011-01-20 |
—
|
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: 2011-01-20 | Statement: [Ed Balls, shadowOfficeStart, 2011-01-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shadowOfficeStart Context triple: [Ed Balls, shadowOfficeStart, 2011-01-20]
-
A.
officeStartFor
Indicates the time or date at which an entity begins its term, role, or period of service in an office or official position.
-
B.
officeStart
chosen
Indicates the time or date at which an entity’s term, role, or period of holding office begins.
-
C.
officeStartApproximate
Indicates that the start of a person’s term in office is known only approximately, not as an exact date.
-
D.
notableOfficeStartContext
Indicates the contextual circumstances or conditions (such as time, place, or situation) surrounding the beginning of a notable office or position held by an entity.
-
E.
officeStartAfter
Indicates that one entity’s term or period in office begins after another specified time or event.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90366fda8819083168c93abad27d4 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.