Triple
T5005106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keystone Thrust Fault |
E112471
|
entity |
| Predicate | visibleAs |
P59275
|
FINISHED |
| Object | contact between gray limestone and red sandstone |
—
|
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: contact between gray limestone and red sandstone | Statement: [Keystone Thrust Fault, visibleAs, contact between gray limestone and red sandstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleAs Context triple: [Keystone Thrust Fault, visibleAs, contact between gray limestone and red sandstone]
-
A.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
B.
isVisibleAs
chosen
Indicates that one entity can be perceived or appears to observers under the form, name, or representation of another entity.
-
C.
visibleRemains
Indicates that some physical remnants of an entity or event can still be seen or visually detected.
-
D.
appearsAs
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
E.
accessibleAs
Indicates that one entity can be reached, used, or obtained through another entity, often as an alternative form, route, or representation.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.