Triple
T19347729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euripides’ Heracles |
E483926
|
entity |
| Predicate | likelyDateRangeOfComposition |
P51921
|
FINISHED |
| Object | c. 420–416 BCE |
—
|
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: c. 420–416 BCE | Statement: [Euripides’ Heracles, likelyDateRangeOfComposition, c. 420–416 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyDateRangeOfComposition Context triple: [Euripides’ Heracles, likelyDateRangeOfComposition, c. 420–416 BCE]
-
A.
formedBetween
Indicates a relationship in which a connection, bond, or structure has come into existence linking two or more entities.
-
B.
createdBetween
chosen
Indicates that something was created within a specified start and end time or date range.
-
C.
occurredBetween
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
-
D.
hasUnknownExactDateOfComposition
Indicates that the precise date when a work was composed is not known.
-
E.
concludedBetween
Indicates that an agreement, arrangement, or formal relationship has been finalized between two or more parties.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185c95248190b1e5bb8626489767 |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.