Triple
T31047341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazonian craton |
E791164
|
entity |
| Predicate | containsRocksFrom |
P156265
|
FINISHED |
| Object | Paleoproterozoic |
—
|
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: Paleoproterozoic | Statement: [Amazonian craton, containsRocksFrom, Paleoproterozoic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRocksFrom Context triple: [Amazonian craton, containsRocksFrom, Paleoproterozoic]
-
A.
containsRocksDated
chosen
Indicates that one entity includes rocks whose ages have been determined through geological dating.
-
B.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
C.
hasRock
Indicates that one entity possesses, contains, or is associated with a rock.
-
D.
hasRockRecordIn
Indicates that an entity has a recorded instance or documentation of rock-related data, activity, or presence within a specified context or location.
-
E.
hasRockGrade
Indicates that an entity is associated with a specific difficulty or quality grade used to classify rock climbing routes or rock features.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
Created at: April 29, 2026, 8:59 p.m.