Triple
T22548937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterpocket Fold monocline |
E557504
|
entity |
| Predicate | dominantStructuralStyle |
P17382
|
FINISHED |
| Object | monoclinal flexure |
—
|
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: monoclinal flexure | Statement: [Waterpocket Fold monocline, dominantStructuralStyle, monoclinal flexure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantStructuralStyle Context triple: [Waterpocket Fold monocline, dominantStructuralStyle, monoclinal flexure]
-
A.
dominantStructure
Indicates that one structure exerts primary control, influence, or prominence over other related structures within a given context.
-
B.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
C.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
D.
dominantComposition
Indicates that one entity is the primary or prevailing component, material, or element that makes up or characterizes another entity.
-
E.
dominantFormOf
chosen
Indicates that one form of something is the primary, prevailing, or most influential version relative to another form.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f372df48190ae5dd461b1230bc7 |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.