Triple
T5661248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Anatolian Fault zone |
E124744
|
entity |
| Predicate | stressRegime |
P65606
|
FINISHED |
| Object | strike-slip dominated |
—
|
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: strike-slip dominated | Statement: [North Anatolian Fault zone, stressRegime, strike-slip dominated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stressRegime Context triple: [North Anatolian Fault zone, stressRegime, strike-slip dominated]
-
A.
stressed
Indicates that an entity is experiencing psychological or emotional strain or pressure, often due to challenging or demanding circumstances.
-
B.
strainType
Indicates the specific variety or subtype classification within a broader category of strains (e.g., biological, chemical, or product strains).
-
C.
pressureType
Indicates the specific category or kind of pressure associated with an entity or interaction.
-
D.
stressesInstitution
Indicates that an entity applies pressure, demands, or strain on an institution, challenging its capacity, stability, or resources.
-
E.
strength
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
- F. None of above. chosen
Provenance (4 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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c0236af5308190b3d698eadf7bcd2b |
completed | March 22, 2026, 5:14 p.m. |
Created at: March 22, 2026, 3:42 p.m.