Triple
T28439506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnaeus Cornelius Lentulus Clodianus |
E715666
|
entity |
| Predicate | campaignResult |
P50967
|
FINISHED |
| Object | defeat by Spartacus |
—
|
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: defeat by Spartacus | Statement: [Gnaeus Cornelius Lentulus Clodianus, campaignResult, defeat by Spartacus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignResult Context triple: [Gnaeus Cornelius Lentulus Clodianus, campaignResult, defeat by Spartacus]
-
A.
campaignOutcome
chosen
Indicates the result or consequence of a campaign, expressing how the campaign ultimately turned out or what it achieved.
-
B.
politicalOutcome
Indicates the result or consequence of a political process, decision, event, or interaction.
-
C.
hasElectionResult
Indicates that a specific election produced a particular outcome or set of results for a candidate, party, or option.
-
D.
electionWinner
Indicates that the subject is the candidate who received the highest support and officially won a particular election.
-
E.
popularVoteOutcome
Indicates the result of a popular vote, specifying which option or candidate received the majority or winning share of votes.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 1:45 a.m.