Triple
T34933276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emerson fault |
E1007499
|
entity |
| Predicate | linkedRuptureSequence |
P147347
|
FINISHED |
| Object | Landers fault system |
—
|
NE NERFINISHED |
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: Landers fault system | Statement: [Emerson fault, linkedRuptureSequence, Landers fault system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedRuptureSequence Context triple: [Emerson fault, linkedRuptureSequence, Landers fault system]
-
A.
linkedOrder
Indicates that one order is associated with or connected to another order in a defined relationship.
-
B.
rupturedSegmentOf
chosen
Indicates that one entity is a segment that has undergone rupture and is part of, or derived from, another entity.
-
C.
associatedBreak
Indicates a relationship where one entity is linked to a specific break, interruption, or pause that is relevant to its state, schedule, or operation.
-
D.
linkedByStructure
Indicates that two entities are connected or associated through a shared structural element, configuration, or framework.
-
E.
linkedPosition
Indicates that one position is associated or connected to another position in a defined way.
- 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: May 3, 2026, 4 p.m.