Triple
T36856411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yilgarn Craton and Pilbara Craton region |
E910806
|
entity |
| Predicate | containsRock |
P1326
|
FINISHED |
| Object | granite-greenstone terranes |
—
|
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: granite-greenstone terranes | Statement: [Yilgarn Craton and Pilbara Craton region, containsRock, granite-greenstone terranes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRock Context triple: [Yilgarn Craton and Pilbara Craton region, containsRock, granite-greenstone terranes]
-
A.
hasRockType
chosen
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
B.
hasRock
Indicates that one entity possesses, contains, or is associated with a rock.
-
C.
hasNearbyRockFormation
Indicates that one entity is located close to or adjacent to a rock formation.
-
D.
hasRockyTerrain
Indicates that the subject possesses or is characterized by rough, uneven, or rock-covered ground or surface conditions.
-
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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0144c75aec81908bdd9e88f2af737a |
completed | May 11, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_6a014405a2d48190a1d58b0b907ad696 |
completed | May 11, 2026, 2:50 a.m. |
Created at: May 3, 2026, 4:13 p.m.