Triple
T33943711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catalan regional elections |
E870233
|
entity |
| Predicate | notablePartyFamily |
P206743
|
FINISHED |
| Object | pro-independence parties |
—
|
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: pro-independence parties | Statement: [Catalan regional elections, notablePartyFamily, pro-independence parties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePartyFamily Context triple: [Catalan regional elections, notablePartyFamily, pro-independence parties]
-
A.
notableFamilyFor
Indicates that a family is particularly recognized or distinguished for a specific person, achievement, role, or characteristic.
-
B.
notableLeaderFamily
Indicates that a person belongs to the family of a notable or prominent leader.
-
C.
notableFamilyIn
Indicates that a person is notably associated with or belongs to a particular family within a given place or context.
-
D.
notableParty
Indicates that an entity is a significant or noteworthy participant in an event, activity, or relationship.
-
E.
associatedPoliticalFamily
Indicates a relationship where an entity is linked or connected to a particular political family, dynasty, or lineage.
- F. None of above. chosen
Provenance (4 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.