Triple
T153762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servant of the People |
E3486
|
entity |
| Predicate | registeredAsPoliticalParty |
P7695
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Servant of the People, registeredAsPoliticalParty, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registeredAsPoliticalParty Context triple: [Servant of the People, registeredAsPoliticalParty, 2018]
-
A.
politicalParty
Indicates that an entity is affiliated with, belongs to, or is a member of a specific political party.
-
B.
politicalSupporter
Indicates that one entity supports, endorses, or aligns with the political views, actions, or position of another entity.
-
C.
endedPoliticalEntity
Indicates that one political entity brought about the termination or dissolution of another political entity.
-
D.
partyRepresentation
Indicates that one party acts on behalf of, or serves as the representative of, another party in a given context or proceeding.
-
E.
partySystemRole
Indicates the specific functional role or capacity that a party assumes within a given system or context.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258e0b11c8190b7b5cf3c354c47ce |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2565c727c8190bca9ba6ca52f216a |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a258de46888190835db2b21a093eaa |
completed | Feb. 28, 2026, 2:54 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.