Triple
T2515116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Antarctic craton basement |
E55393
|
entity |
| Predicate | ageEvidence |
P3168
|
FINISHED |
| Object | radiometric dating of basement rocks |
—
|
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: radiometric dating of basement rocks | Statement: [East Antarctic craton basement, ageEvidence, radiometric dating of basement rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageEvidence Context triple: [East Antarctic craton basement, ageEvidence, radiometric dating of basement rocks]
-
A.
archaeologicalEvidenceAge
Indicates the age or time period to which a piece of archaeological evidence is dated.
-
B.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
C.
agePattern
Indicates a relationship where entities share or follow a specific configuration, distribution, or rule regarding their ages.
-
D.
ageProgression
Indicates a temporal relationship where an entity’s age increases or advances over time.
-
E.
usedEvidenceType
chosen
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0bf37c0819088d28b5081ba7556 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.