Triple
T342551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Uplands Fault |
E6866
|
entity |
| Predicate | typeOfBoundary |
P1972
|
FINISHED |
| Object | structural and lithological boundary |
—
|
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: structural and lithological boundary | Statement: [Southern Uplands Fault, typeOfBoundary, structural and lithological boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBoundary Context triple: [Southern Uplands Fault, typeOfBoundary, structural and lithological boundary]
-
A.
hasBoundaryType
chosen
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
B.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
C.
dimensionBoundType
Indicates the type or nature of the constraint that bounds a given dimension in a relationship.
-
D.
demarcationType
Indicates the specific way in which a boundary or separation between entities is defined, marked, or categorized.
-
E.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eafef8c88190a5932eb2c6ac4a5d |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95197fc8190820e8ebd0d7d27fa |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.