Triple
T27855117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DP |
E704061
|
entity |
| Predicate | opposedDominantParty |
P63568
|
FINISHED |
| Object | National 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: National Party | Statement: [DP, opposedDominantParty, National Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedDominantParty Context triple: [DP, opposedDominantParty, National Party]
-
A.
dominantParty
Indicates that one party in a relationship holds primary control, authority, or influence over the other.
-
B.
opposesPartyType
Indicates that one party or entity is in opposition to, or acts against the interests or positions of, a particular type or category of party.
-
C.
opposedPoliticalEntity
chosen
Indicates that one political entity is in opposition or conflict with another in terms of policies, ideology, or power.
-
D.
notableOppositionParty
Indicates that an entity is recognized as a significant or prominent opposition political party relative to a given political system or governing body.
-
E.
primaryPoliticalOppositionFrom
Indicates that one entity serves as the main or leading political opponent or source of political opposition to another entity.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 27, 2026, 6:13 p.m.