Triple
T33085736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loma Prieta |
E846633
|
entity |
| Predicate | componentMeaning_loma |
P45905
|
FINISHED |
| Object | hill |
—
|
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: hill | Statement: [Loma Prieta, componentMeaning_loma, hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentMeaning_loma Context triple: [Loma Prieta, componentMeaning_loma, hill]
-
A.
logicalMeaning
Indicates that one entity expresses, encodes, or conveys the logical content, implication, or formal meaning of another.
-
B.
centralFormulaMeaning
Indicates that one formula or expression represents the primary or core meaning within a larger logical, mathematical, or semantic structure.
-
C.
objectMeaning
Indicates that one entity represents, expresses, or conveys the meaning or semantic content of another entity.
-
D.
nodeMeaning
Indicates that one entity represents, defines, or conveys the semantic content or intended meaning of another entity.
-
E.
stringMeaning
chosen
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
- 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_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 1, 2026, 1:26 a.m.