Triple
T25868143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1876 Louisiana gubernatorial election |
E651675
|
entity |
| Predicate | resultStatus |
P158784
|
FINISHED |
| Object | contested |
—
|
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: contested | Statement: [1876 Louisiana gubernatorial election, resultStatus, contested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultStatus Context triple: [1876 Louisiana gubernatorial election, resultStatus, contested]
-
A.
returnStatus
Indicates the current outcome or condition of a previously initiated return action or process.
-
B.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
C.
resolutionStatus
chosen
Indicates the current state or outcome of how an issue, request, or case has been addressed or resolved.
-
D.
resultUsage
Indicates how the outcome or result of an action, process, or event is used, applied, or consumed in relation to another entity or context.
-
E.
resultDetermination
Indicates the process or criteria by which an outcome, decision, or result is established or concluded from given inputs or conditions.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 22, 2026, 8:07 a.m.