Triple
T15833075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chris Hipkins |
E383918
|
entity |
| Predicate | parliamentary term start |
P94662
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Chris Hipkins, parliamentary term start, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentary term start Context triple: [Chris Hipkins, parliamentary term start, 2008]
-
A.
parliamentaryTermStarted
chosen
Indicates that a specific parliamentary term has begun for a legislative body or member.
-
B.
parliamentaryTerm
Indicates the specific legislative session or fixed period of time during which a parliament is formally in office and exercises its authority.
-
C.
rajyaSabhaTermStart
Indicates the date on which an individual's term as a member of the Rajya Sabha (the upper house of India's Parliament) begins.
-
D.
termInEuropeanParliamentStart
Indicates the date or time at which an entity’s term of service in the European Parliament begins.
-
E.
parliamentaryTermType
Indicates the specific category or classification of a parliamentary term within a legislative or governmental context.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e653e388190a4696cdb22546715 |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.