Triple
T33413173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Churchill (biography) |
E855642
|
entity |
| Predicate | subjectPoliticalPartyDescribed |
P114263
|
FINISHED |
| Object | Conservative Party (UK) |
—
|
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: Conservative Party (UK) | Statement: [Churchill (biography), subjectPoliticalPartyDescribed, Conservative Party (UK)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectPoliticalPartyDescribed Context triple: [Churchill (biography), subjectPoliticalPartyDescribed, Conservative Party (UK)]
-
A.
subjectPoliticalParty
chosen
Indicates the political party with which the subject is formally affiliated or identified.
-
B.
politicalParty
Indicates that an entity is affiliated with, belongs to, or is a member of a specific political party.
-
C.
partnerPoliticalAffiliation
Indicates that one entity has a political affiliation that is associated with, or shared by, its partner entity.
-
D.
ledPoliticalParty
Indicates that one entity served as the leader or head of a particular political party.
-
E.
describesPoliticalParty
Indicates that one entity provides a description or characterization of a political party.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 1, 2026, 1:36 a.m.