Triple
T33085742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loma Prieta |
E846633
|
entity |
| Predicate | etymologicalOrigin_prieta |
P58900
|
FINISHED |
| Object | Spanish adjective "prieto/prieta" |
—
|
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: Spanish adjective "prieto/prieta" | Statement: [Loma Prieta, etymologicalOrigin_prieta, Spanish adjective "prieto/prieta"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologicalOrigin_prieta Context triple: [Loma Prieta, etymologicalOrigin_prieta, Spanish adjective "prieto/prieta"]
-
A.
traditionalEtymology
Indicates that an entity’s origin or meaning is explained according to a historically established or customary etymological account.
-
B.
etymologyProposedBy
Indicates that a proposed origin or derivation of a word or term is attributed to a particular person or source.
-
C.
historicalOriginMeaning
Indicates that one entity explains the original historical source or derivational meaning of another entity.
-
D.
etymologicalRootName
Indicates that one name is derived from, or originates etymologically in, another name.
-
E.
etymologicalNote
chosen
Indicates that there is a note explaining the origin, historical development, or source language of a term or name.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:26 a.m.