Triple
T28662716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casca |
E725508
|
entity |
| Predicate | eventDateParticipatedIn |
P96386
|
FINISHED |
| Object | 44 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: 44 BC | Statement: [Casca, eventDateParticipatedIn, 44 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDateParticipatedIn Context triple: [Casca, eventDateParticipatedIn, 44 BC]
-
A.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
-
B.
participatedInEvent
Indicates that an entity took part in or was actively involved in a specific event.
-
C.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
-
D.
yearOfEventParticipation
chosen
Indicates the specific calendar year in which an entity participated in a particular event.
-
E.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 4:59 a.m.