Triple
T30972204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwe Craton |
E789128
|
entity |
| Predicate | timeSpanOfGreenstoneBelts |
P43544
|
FINISHED |
| Object | ~3.5–2.6 Ga |
—
|
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: ~3.5–2.6 Ga | Statement: [Zimbabwe Craton, timeSpanOfGreenstoneBelts, ~3.5–2.6 Ga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpanOfGreenstoneBelts Context triple: [Zimbabwe Craton, timeSpanOfGreenstoneBelts, ~3.5–2.6 Ga]
-
A.
orogenyTimeSpan
Indicates the time interval during which an orogenic (mountain-building) event occurred.
-
B.
timeSpanOfExcavations
Indicates the duration or period of time during which the excavations took place.
-
C.
geologicalTimeBoundaryWithin
Indicates that one geological time boundary occurs entirely within the temporal span defined by another geological time boundary.
-
D.
geologicalAge
Indicates the time period in Earth's geological history during which an entity (such as a rock, fossil, or formation) originated or was formed.
-
E.
geologicalRange
chosen
Indicates the span of geological time during which an entity (such as a taxon or formation) is known to have existed or been present.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 8:55 p.m.