Triple
T8310187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Catilinam |
E194571
|
entity |
| Predicate | numberOfSpeeches |
P82677
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [In Catilinam, numberOfSpeeches, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSpeeches Context triple: [In Catilinam, numberOfSpeeches, 4]
-
A.
reportsSpeechesOf
Indicates that one entity documents, narrates, or provides accounts of the speeches delivered by another entity.
-
B.
hasApproximateTotalSpeakers
Indicates that an entity is associated with an estimated or roughly calculated number of total speakers, rather than an exact count.
-
C.
spokeAt
Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
-
D.
hasSpeakersAmong
Indicates that a group, event, or entity includes one or more speakers drawn from a specified set or category.
-
E.
spokenOn
Indicates that an utterance or speech act occurred at or during a specific time or date.
- 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.