Triple
T32014727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MSP |
E817502
|
entity |
| Predicate | successorIdeologicalLineage |
P177222
|
FINISHED |
| Object | Virtue Party |
—
|
NE NERFINISHED |
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: Virtue Party | Statement: [MSP, successorIdeologicalLineage, Virtue Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorIdeologicalLineage Context triple: [MSP, successorIdeologicalLineage, Virtue Party]
-
A.
hasSuccessorIdeology
Indicates that one ideology follows, replaces, or develops from another as its subsequent ideological form or movement.
-
B.
hasSuccessorIdeologicalRoots
Indicates that one entity’s ideological foundations are derived from, influenced by, or developed as a continuation of another entity’s ideology.
-
C.
successorInIdea
Indicates that one idea conceptually follows, develops from, or replaces another in a sequence of intellectual progression.
-
D.
isSuccessorInTraditionTo
chosen
Indicates that one entity follows and continues the practices, ideas, or legacy of another within a particular tradition or lineage.
-
E.
successorLine
Indicates that one line directly follows another in a sequence or ordered arrangement.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
Created at: May 1, 2026, 12:16 a.m.