Triple
T8716729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Boundary Thrust zone |
E206913
|
entity |
| Predicate | displaces |
P51873
|
FINISHED |
| Object | Siwalik Group sediments |
—
|
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: Siwalik Group sediments | Statement: [Main Boundary Thrust zone, displaces, Siwalik Group sediments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displaces Context triple: [Main Boundary Thrust zone, displaces, Siwalik Group sediments]
-
A.
displacement
Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
-
B.
displacedBy
Indicates that one entity has been moved, replaced, or forced out of its original position, role, or state by another entity.
-
C.
displacementCategory
Indicates the type or classification of a displacement event or condition associated with an entity.
-
D.
displacementVariant
Indicates a relationship where one entity is an alternative or modified form of another that differs specifically in its spatial position or displacement.
-
E.
displacementCause
chosen
Indicates a causal relationship where one entity is responsible for the displacement or forced movement of another entity from its original location or situation.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd9c2a08190a65ab0ce573153d2 |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.