Triple
T1996561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Uplands accretionary prism |
E43372
|
entity |
| Predicate | deformationFeatures |
P35342
|
FINISHED |
| Object | thrust faults |
—
|
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: thrust faults | Statement: [Southern Uplands accretionary prism, deformationFeatures, thrust faults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deformationFeatures Context triple: [Southern Uplands accretionary prism, deformationFeatures, thrust faults]
-
A.
deformationStyle
Indicates the manner or pattern in which an object or material is deformed under applied forces or conditions.
-
B.
hasInternalDeformation
Indicates that one entity exhibits structural distortion or change within its interior caused by stress, force, or other internal factors.
-
C.
reconstructionFeature
Indicates that one entity serves as a feature, component, or characteristic used in the reconstruction or restoration of another entity.
-
D.
featuresDecor
Indicates that one entity includes or showcases the decor elements provided or defined by another entity.
-
E.
skeletonFeature
Indicates that one entity is a structural or anatomical skeletal feature or component of another entity.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb79c97d48190b3147430ed39faa9 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb90ec7948190bbfb0329e9e67cca |
completed | March 7, 2026, 5:35 a.m. |
Created at: March 4, 2026, 7:37 p.m.