Triple
T21637687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Rights Protection Party |
E534002
|
entity |
| Predicate | wasInGovernment |
P31613
|
FINISHED |
| Object | 1982–2021 |
—
|
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: 1982–2021 | Statement: [Human Rights Protection Party, wasInGovernment, 1982–2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasInGovernment Context triple: [Human Rights Protection Party, wasInGovernment, 1982–2021]
-
A.
servedInGovernmentWith
Indicates that two individuals held positions in the same government or administration during an overlapping period of time.
-
B.
hasBeenInGovernmentUntil
chosen
Indicates that an entity held a government position continuously up to a specified end time or date.
-
C.
heldPoliticalOfficeIn
Indicates that an entity served in a political office or position within a specified governmental body or jurisdiction.
-
D.
workedUnderGovernmentOf
Indicates that an entity was employed by, served within, or operated under the authority of a specific government or its administrative bodies.
-
E.
usedInGovernmentBody
Indicates that an entity is employed by, serves within, or is otherwise functionally involved in the operations of a government body.
- 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef538eef0481908f5bf0e27f8e054d |
completed | April 27, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.