Triple
T29681773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph Cook |
E750969
|
entity |
| Predicate | termInOfficeAs |
P17403
|
FINISHED |
| Object | Prime Minister of Australia |
—
|
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: Prime Minister of Australia | Statement: [Joseph Cook, termInOfficeAs, Prime Minister of Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termInOfficeAs Context triple: [Joseph Cook, termInOfficeAs, Prime Minister of Australia]
-
A.
termInOffice
chosen
Indicates the period during which an individual officially holds a particular office or position.
-
B.
termInOfficeContext
Indicates that one entity’s tenure or period of holding an office, role, or position is being specified or contextualized in relation to another entity or timeframe.
-
C.
numberOfTermInOffice
Indicates the specific ordinal count of how many terms an entity has served in a particular office or position.
-
D.
remainedInOfficeAs
Indicates that one entity continued to hold the same official position or role as another entity, without interruption, over a given period.
-
E.
appointedTerm
Indicates that an entity has been officially assigned to hold a position or role for a specified term or duration.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 7:10 p.m.