Triple
T5661247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Anatolian Fault zone |
E124744
|
entity |
| Predicate | faultTypeDetail |
P3827
|
FINISHED |
| Object | continental transform fault |
—
|
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: continental transform fault | Statement: [North Anatolian Fault zone, faultTypeDetail, continental transform fault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faultTypeDetail Context triple: [North Anatolian Fault zone, faultTypeDetail, continental transform fault]
-
A.
typeOfFaulting
chosen
Indicates the kind or classification of geological faulting that characterizes the relationship between rock units or structures.
-
B.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
-
C.
errorType
Indicates the specific category or kind of error associated with an event, action, or entity.
-
D.
associatedFault
Indicates a relationship where a given entity is linked to, or occurs in connection with, a specific fault or error condition.
-
E.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
- 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_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. |
Created at: March 22, 2026, 3:42 p.m.