Triple
T15598854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gentius |
E374975
|
entity |
| Predicate | politicalStatusAfterDefeat |
P86247
|
FINISHED |
| Object | Roman prisoner |
—
|
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: Roman prisoner | Statement: [Gentius, politicalStatusAfterDefeat, Roman prisoner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalStatusAfterDefeat Context triple: [Gentius, politicalStatusAfterDefeat, Roman prisoner]
-
A.
politicalStatusAfterEvent
chosen
Indicates the political status or condition an entity holds as a result of, or following, a specific event.
-
B.
legalStatusAfterCoup
Indicates the legal status or standing of an entity following a coup or unconstitutional change of power.
-
C.
formedAfterElection
Indicates that an entity (such as a government, cabinet, or committee) was established or came into existence following the conclusion of an election.
-
D.
politicalStatusAtEnd
Indicates the political status or condition an entity holds at the conclusion of a specified event or time period.
-
E.
defeatedCandidate
Indicates that one candidate has won an election or contest against another candidate, causing the other to lose.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e609ab081909feb486a57439960 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.