Triple
T12628769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitlis–Zagros suture zone |
E301584
|
entity |
| Predicate | majorPhaseOfCollision |
P7628
|
FINISHED |
| Object | Miocene |
—
|
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: Miocene | Statement: [Bitlis–Zagros suture zone, majorPhaseOfCollision, Miocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorPhaseOfCollision Context triple: [Bitlis–Zagros suture zone, majorPhaseOfCollision, Miocene]
-
A.
majorPhase
Indicates that one phase is a primary or dominant stage within a larger process, lifecycle, or sequence.
-
B.
majorCapturePhase
Indicates a significant or primary stage in a capture process where the main act of seizing, acquiring, or taking control occurs.
-
C.
accidentPhase
Indicates the specific stage or phase of progression within an accident or incident event.
-
D.
mainPhase
chosen
Indicates that an event, action, or state occurs during the primary or central phase of a larger process or sequence.
-
E.
majorPhaseCompletion
Indicates that a significant or primary phase of a larger process, project, or lifecycle has been fully completed.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:15 p.m.