Triple
T8491482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Country party |
E200979
|
entity |
| Predicate | hadStanceOn |
P56202
|
FINISHED |
| Object | limiting royal patronage |
—
|
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: limiting royal patronage | Statement: [Country party, hadStanceOn, limiting royal patronage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadStanceOn Context triple: [Country party, hadStanceOn, limiting royal patronage]
-
A.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
-
B.
hadVoteIn
Indicates that an entity participated by casting a vote in a particular decision, election, or voting event.
-
C.
hasPoliticalPositionOn
chosen
Indicates that an entity holds or expresses a specific stance, view, or opinion regarding a political issue, policy, or topic.
-
D.
hasDebatedStatus
Indicates that an entity has participated in or been assigned a particular status related to a debate or debating activity.
-
E.
oppositionStatus
Indicates that one entity’s stance, condition, or role is characterized by being against, resisting, or in conflict with another entity, proposal, or situation.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe55af3f48190a8cd64cdce0ebd4c |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.