Triple
T1260230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SDP–Liberal Alliance |
E12480
|
entity |
| Predicate | soughtToAppealTo |
P14484
|
FINISHED |
| Object | moderate voters |
—
|
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: moderate voters | Statement: [SDP–Liberal Alliance, soughtToAppealTo, moderate voters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soughtToAppealTo Context triple: [SDP–Liberal Alliance, soughtToAppealTo, moderate voters]
-
A.
alsoAppealsTo
chosen
Indicates that something attracts, interests, or is pleasing to an additional person, group, or audience beyond the primary one.
-
B.
wantedBy
Indicates that one entity is desired, sought, or wished for by another entity.
-
C.
aimsToProvide
Indicates that one entity intends or is designed to supply, deliver, or make available something to another entity.
-
D.
aimsToSolve
Indicates an intention or purpose directed toward resolving, addressing, or eliminating a particular problem, challenge, or issue.
-
E.
secondaryAudience
Indicates that an entity is a secondary or additional intended audience or target group for another entity (such as a work, message, or product), beyond the primary audience.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc503e88190b237210a61228dd8 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6eefbc81908dddd7d2ef368186 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.