Triple
T14030677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thera eruption |
E337577
|
entity |
| Predicate | radiocarbonDateRange |
P82593
|
FINISHED |
| Object | circa 1627–1600 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: circa 1627–1600 BCE | Statement: [Thera eruption, radiocarbonDateRange, circa 1627–1600 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radiocarbonDateRange Context triple: [Thera eruption, radiocarbonDateRange, circa 1627–1600 BCE]
-
A.
radiocarbonDatingPerformed
Indicates that radiocarbon dating has been carried out on an entity to determine its age or time period.
-
B.
chronologicalRange
chosen
Indicates the temporal span or period over which something occurs, is valid, or is relevant.
-
C.
approximateAgeBeforePresent
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
D.
archaeologicalEvidenceAge
Indicates the age or time period to which a piece of archaeological evidence is dated.
-
E.
chronologicalUncertainty
Indicates that the timing or chronological order of an event or relationship is uncertain or not precisely known.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa9f8248190930954d609dee5f1 |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.