Triple
T1032410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homeric Hymns |
E22280
|
entity |
| Predicate | earliestPossibleDate |
P288
|
FINISHED |
| Object | 7th 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 century BCE | Statement: [Homeric Hymns, earliestPossibleDate, 7th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestPossibleDate Context triple: [Homeric Hymns, earliestPossibleDate, 7th century BCE]
-
A.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
B.
earliestState
Indicates that one state or condition occurs before all other related states in time, representing the earliest point in a sequence.
-
C.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
-
D.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
E.
earliestStage
Indicates that one entity represents the first or minimum stage, phase, or step in a defined ordered sequence relative to another.
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8d669448190955507e2e4975b9f |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b728ad3481909cf1430349cb9bba |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.