Triple
T28486378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | neoconservatism |
E720841
|
entity |
| Predicate | isAssociatedWithParty |
P2830
|
FINISHED |
| Object | Republican 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: Republican Party | Statement: [neoconservatism, isAssociatedWithParty, Republican Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssociatedWithParty Context triple: [neoconservatism, isAssociatedWithParty, Republican Party]
-
A.
associatedWithPartySystem
Indicates that an entity is linked or connected to a particular party system, such as a political or organizational party structure.
-
B.
isNamedAsPartyIn
Indicates that an entity is explicitly listed or designated as a party in a formal agreement, contract, or legal document.
-
C.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
D.
arePartyTo
Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
-
E.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f0fbb688190a5c1f5ff50f6f7df |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 2:58 a.m.