Triple
T4048755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Party (South Africa) |
E84131
|
entity |
| Predicate | startTimeOfHeldOffice |
P18957
|
FINISHED |
| Object | 1934 |
—
|
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: 1934 | Statement: [United Party (South Africa), startTimeOfHeldOffice, 1934]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfHeldOffice Context triple: [United Party (South Africa), startTimeOfHeldOffice, 1934]
-
A.
officeHolderStartTime
Indicates the date and time at which an individual begins holding a particular office or position.
-
B.
lastOfficeHolderStartDate
Indicates the date on which the most recent person to hold a particular office or position began their term.
-
C.
timeInOfficeBeginsIn
chosen
Indicates the point in time or date when an entity’s term, tenure, or period in office starts.
-
D.
termInOffice
Indicates the period during which an individual officially holds a particular office or position.
-
E.
startTimeAsUSCongressSeat
Indicates the date and time at which an individual officially begins serving in a specific seat in the U.S. Congress.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb82d1a08190aa8c5c48d368b58b |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.