Triple
T34933221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airport Lake fault zone |
E1007497
|
entity |
| Predicate | hasLithologyContext |
P66011
|
FINISHED |
| Object | continental crust |
—
|
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: continental crust | Statement: [Airport Lake fault zone, hasLithologyContext, continental crust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLithologyContext Context triple: [Airport Lake fault zone, hasLithologyContext, continental crust]
-
A.
hasCrustalContext
chosen
Indicates that something is associated with, situated within, or characterized by a particular geological crustal setting or context.
-
B.
lithologyAffected
Indicates that one lithology is influenced, altered, or impacted in some way by another geological process, material, or condition.
-
C.
lithology
Indicates the type and characteristics of rock or sediment that compose a geological unit or layer.
-
D.
lithologyInfluence
Indicates how the type and characteristics of rock or sediment affect geological or environmental properties, processes, or patterns.
-
E.
lithologyAbove
Indicates that one rock or sediment layer directly overlies another in a vertical stratigraphic sequence.
- 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: May 3, 2026, 4 p.m.