Triple
T28793604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De oratore, Book I |
E727024
|
entity |
| Predicate | timeOfFictionalConversation |
P60994
|
FINISHED |
| Object | 91 BC |
—
|
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: 91 BC | Statement: [De oratore, Book I, timeOfFictionalConversation, 91 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfFictionalConversation Context triple: [De oratore, Book I, timeOfFictionalConversation, 91 BC]
-
A.
timeOfDialogue
Indicates the specific time or temporal context at which a dialogue or conversational exchange occurs.
-
B.
timeOfNarrative
Indicates the specific time or period during which the events of a narrative are set or unfold.
-
C.
fictionalTime
chosen
Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
-
D.
timeOfMonologue
Indicates the specific time at which a monologue occurs or is delivered.
-
E.
fictionalTimeDepth
Indicates a relationship where an entity is associated with a time period or temporal depth that exists only within a fictional or imagined context.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 6:24 a.m.