Triple
T5804174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hymn to Aphrodite |
E128699
|
entity |
| Predicate | probableDateRange |
P51921
|
FINISHED |
| Object | 7th–6th century 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: 7th–6th century BCE | Statement: [Hymn to Aphrodite, probableDateRange, 7th–6th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: probableDateRange Context triple: [Hymn to Aphrodite, probableDateRange, 7th–6th century BCE]
-
A.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
B.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
C.
representsDateRange
Indicates that a subject is associated with, valid for, or applicable during a specific start-to-end date range.
-
D.
concludedBetween
Indicates that an agreement, arrangement, or formal relationship has been finalized between two or more parties.
-
E.
createdBetween
chosen
Indicates that something was created within a specified start and end time or date range.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1304588190b59a18fb7b70a60f |
completed | March 22, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.