Triple
T29947904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calaveras Fault |
E760687
|
entity |
| Predicate | faultSystemRole |
P12085
|
FINISHED |
| Object | major branch of the San Andreas system |
—
|
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: major branch of the San Andreas system | Statement: [Calaveras Fault, faultSystemRole, major branch of the San Andreas system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faultSystemRole Context triple: [Calaveras Fault, faultSystemRole, major branch of the San Andreas system]
-
A.
systemRole
chosen
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
B.
basisRole
Indicates that one role serves as the foundational or underlying role upon which another role or function is defined or derived.
-
C.
FDARole
Indicates a role or function that an entity holds within the context of FDA-related responsibilities, authority, or activities.
-
D.
roleInMalfunkshun
Indicates that an entity holds or held a specific role or position within the band Malfunkshun.
-
E.
formRole
Indicates that an entity assumes, is assigned, or functions in a particular role within a specified context or structure.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6780d1b948190a1a8ca4f34d93cb3 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:24 p.m.