Triple
T530423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Age |
E12209
|
entity |
| Predicate | timeSpanApproximateEnd |
P8204
|
FINISHED |
| Object | 1st millennium BCE in much of the Mediterranean |
—
|
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: 1st millennium BCE in much of the Mediterranean | Statement: [Iron Age, timeSpanApproximateEnd, 1st millennium BCE in much of the Mediterranean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpanApproximateEnd Context triple: [Iron Age, timeSpanApproximateEnd, 1st millennium BCE in much of the Mediterranean]
-
A.
hasApproximateEnd
chosen
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
B.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b257108190a537dffbb9d621b5 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.