Triple
T31688835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriotic Movement |
E808731
|
entity |
| Predicate | roleWithinParty |
P59265
|
FINISHED |
| Object | internal faction |
—
|
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: internal faction | Statement: [Patriotic Movement, roleWithinParty, internal faction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleWithinParty Context triple: [Patriotic Movement, roleWithinParty, internal faction]
-
A.
intraPartyRole
chosen
Indicates a role or function that an entity holds within a specific political party or internal party structure.
-
B.
partySystemRole
Indicates the specific functional role or capacity that a party assumes within a given system or context.
-
C.
roleInCongress
Indicates the specific position or function an individual holds within a legislative congress.
-
D.
partnerPoliticalAffiliation
Indicates that one entity has a political affiliation that is associated with, or shared by, its partner entity.
-
E.
registeredAsPoliticalParty
Indicates that an entity is officially recorded and recognized as a political party by the relevant authority or registry.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:07 p.m.