Triple
T19433506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ochil Fault |
E486175
|
entity |
| Predicate | hasThrownDownTo |
P12063
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Ochil Fault, hasThrownDownTo, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThrownDownTo Context triple: [Ochil Fault, hasThrownDownTo, south]
-
A.
stoodDown
Indicates that an entity relinquished its active role, position, or state of readiness, often stepping aside from duty or responsibility.
-
B.
downthrowSide
chosen
Indicates the side of a fault or geological structure on which the rock mass has moved downward relative to the opposite side.
-
C.
shotDownOver
Indicates that one entity caused another (typically an aircraft or projectile) to be brought down while it was in flight above a particular location or area.
-
D.
wasThrownFrom
Indicates that an entity was propelled away or ejected from another entity, typically by a forceful or intentional throwing action.
-
E.
descendedTo
Indicates that one entity has moved or traveled downward to reach the location or level of 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6335dae10819096e1825741f814ed |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.