Triple
T29175875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insular Orogeny |
E739607
|
entity |
| Predicate | involvesTerrane |
P183113
|
FINISHED |
| Object | Insular Superterrane |
—
|
NE NERFINISHED |
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: Insular Superterrane | Statement: [Insular Orogeny, involvesTerrane, Insular Superterrane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesTerrane Context triple: [Insular Orogeny, involvesTerrane, Insular Superterrane]
-
A.
containedTerrane
Indicates that one geological terrane is spatially contained within the boundaries of another terrane.
-
B.
containsTerranesFrom
Indicates that a geological unit or region includes within it distinct terranes originating from the specified source area or areas.
-
C.
separatesRockTerranes
Indicates a geological boundary or feature that divides or distinguishes different rock terranes from one another.
-
D.
lithosphericPlatesInvolved
Indicates that specific lithospheric plates participate in or are affected by a particular geological process, interaction, or event.
-
E.
involvedInOrogeny
Indicates involvement in the geological mountain-building process of an orogeny, either as a contributing factor or as a participant in its formation.
- F. None of above. chosen
Provenance (4 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: April 28, 2026, 11:55 a.m.