Triple
T8716697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Central Thrust zone |
E206912
|
entity |
| Predicate | extendsAlongStrike |
P2409
|
FINISHED |
| Object | over 1500 km |
—
|
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: over 1500 km | Statement: [Main Central Thrust zone, extendsAlongStrike, over 1500 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendsAlongStrike Context triple: [Main Central Thrust zone, extendsAlongStrike, over 1500 km]
-
A.
definedAlong
Indicates that one entity is specified, established, or determined in relation to the course, boundary, or extent of another entity.
-
B.
extendsAlongCoastOf
Indicates that one entity stretches or runs parallel along the coastline of another entity.
-
C.
expansionAlongside
Indicates that one entity expands or grows in parallel with, and in relation to, the expansion of another entity.
-
D.
maximumCrustalExtension
Indicates the greatest amount of stretching or thinning that the Earth’s crust has undergone in a given region or event.
-
E.
locatedAlong
chosen
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
- 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.