Triple
T11482622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nationalist Republican Alliance |
E272190
|
entity |
| Predicate | hasElectoralType |
P8161
|
FINISHED |
| Object | catch-all right-wing party |
—
|
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: catch-all right-wing party | Statement: [Nationalist Republican Alliance, hasElectoralType, catch-all right-wing party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectoralType Context triple: [Nationalist Republican Alliance, hasElectoralType, catch-all right-wing party]
-
A.
hasCoralType
Indicates that an entity possesses, is associated with, or is characterized by a specific type or category of coral.
-
B.
electoralType
chosen
Indicates the specific kind or category of electoral process associated with an entity (e.g., general, primary, local, presidential).
-
C.
hasDatePrecision
Indicates that a date value is associated with a specific level of granularity or exactness (such as year, month, day, or time).
-
D.
hasElementType
Indicates that something is composed of or contains elements that are of a specified type.
-
E.
hasRecordType
Indicates that an entity is associated with or classified under a specific type or category of record.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85a1d86b88190b180f6b0d0a27029 |
completed | April 10, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.