Triple
T17944492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Lansbury |
E448668
|
entity |
| Predicate | officeForStartEndTime |
P129825
|
FINISHED |
| Object | Leader of the Labour Party (UK) |
—
|
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: Leader of the Labour Party (UK) | Statement: [George Lansbury, officeForStartEndTime, Leader of the Labour Party (UK)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeForStartEndTime Context triple: [George Lansbury, officeForStartEndTime, Leader of the Labour Party (UK)]
-
A.
officeStartApproximate
Indicates that the start of a person’s term in office is known only approximately, not as an exact date.
-
B.
officeStartQualifier
Indicates a modifier that qualifies or specifies the circumstances, timing, or conditions under which an office term begins.
-
C.
officeStartAfter
Indicates that one entity’s term or period in office begins after another specified time or event.
-
D.
officeEndTimeFor
Indicates the time at which an entity’s office hours or work period end for another specified entity.
-
E.
officeEndApproximate
Indicates that an office or term ended around an approximate date rather than on a precisely known day.
- F. None of above. chosen
Provenance (4 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad9819a88190ad4ea7d562cf3f28 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:21 a.m.