Triple
T1901071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ovid |
E37688
|
entity |
| Predicate | reasonForExile |
P15406
|
FINISHED |
| Object | carmen et error |
—
|
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: carmen et error | Statement: [Ovid, reasonForExile, carmen et error]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForExile Context triple: [Ovid, reasonForExile, carmen et error]
-
A.
causeOfExile
chosen
Indicates the reason or circumstance that led to an entity’s exile.
-
B.
wasExiled
Indicates that an entity was forcibly sent away from their home or country, typically as a punishment or due to political or social pressures.
-
C.
reasonForAbdication
Indicates the specific cause, motive, or circumstances that led an individual to formally abdicate a position of authority or power.
-
D.
traditionallyExiledTo
Indicates that an entity has, by long-standing custom or tradition, been sent away or banished to a particular place.
-
E.
reasonForBan
Indicates the justification or cause that led to an entity being banned.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.