Triple
T32622751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNP |
E833972
|
entity |
| Predicate | hasSucceeded |
P169523
|
FINISHED |
| Object | United National Front (as electoral alliance leader) |
—
|
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: United National Front (as electoral alliance leader) | Statement: [UNP, hasSucceeded, United National Front (as electoral alliance leader)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSucceeded Context triple: [UNP, hasSucceeded, United National Front (as electoral alliance leader)]
-
A.
hasCompleted
Indicates that an entity has finished or successfully carried out a specified task, process, or activity.
-
B.
isSuccessful
Indicates that an action, process, or attempt has achieved its intended goal or outcome.
-
C.
succeededOn
chosen
Indicates that one entity achieved success or a desired outcome specifically in relation to another entity, event, or attempt.
-
D.
succeededUnder
Indicates that one entity achieved success or attained a position while operating under the authority, leadership, or conditions established by another entity.
-
E.
hasMet
Indicates that one entity has encountered or come into contact with another entity at least once.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: May 1, 2026, 1:06 a.m.