Triple
T8716771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indus-Tsangpo Suture Zone |
E206914
|
entity |
| Predicate | hostRockTypes |
P53497
|
FINISHED |
| Object | basalts |
—
|
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: basalts | Statement: [Indus-Tsangpo Suture Zone, hostRockTypes, basalts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostRockTypes Context triple: [Indus-Tsangpo Suture Zone, hostRockTypes, basalts]
-
A.
hostRock
chosen
Indicates that one rock body serves as the surrounding or enclosing rock in which another geological feature (such as an ore deposit, vein, or intrusion) occurs.
-
B.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
C.
rockTypeMarketedAs
Indicates that a particular rock type is promoted or advertised under a specific commercial or trade name.
-
D.
hostType
Indicates the category or kind of host associated with or responsible for the related entity or activity.
-
E.
caveType
Indicates the specific classification or kind of cave associated with an entity.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd9c2a08190a65ab0ce573153d2 |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.