Triple
T8310207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Catilinam |
E194571
|
entity |
| Predicate | firstSpeechFocus |
P82678
|
FINISHED |
| Object | exposing Catiline in the Senate |
—
|
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: exposing Catiline in the Senate | Statement: [In Catilinam, firstSpeechFocus, exposing Catiline in the Senate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSpeechFocus Context triple: [In Catilinam, firstSpeechFocus, exposing Catiline in the Senate]
-
A.
mainSpeechBy
Indicates that a speech or primary address is delivered or given by a particular entity.
-
B.
firstBroadcast
Indicates the date or event of the initial public transmission or airing of a program, signal, or content.
-
C.
firstBroadcastBy
Indicates that one entity is the original broadcaster or channel that first aired the other entity (such as a program, event, or content).
-
D.
firstMessageTo
Indicates that one entity is the initial sender of a message or communication to another entity.
-
E.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f2d2c30819095075940479b75a7 |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:54 p.m.