Triple
T35880891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salton Sea Geothermal Field |
E1037502
|
entity |
| Predicate | explorationMethods |
P55275
|
FINISHED |
| Object | geophysical surveys |
—
|
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: geophysical surveys | Statement: [Salton Sea Geothermal Field, explorationMethods, geophysical surveys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explorationMethods Context triple: [Salton Sea Geothermal Field, explorationMethods, geophysical surveys]
-
A.
explorationBy
Indicates a relationship where one entity conducts or performs exploration directed at or involving another entity.
-
B.
explorationUse
Indicates the use of something specifically for exploration or investigative activities.
-
C.
explorationType
Indicates the specific kind or category of exploration activity associated with an entity or event.
-
D.
exploresFor
Indicates that one entity actively investigates or searches within or on behalf of another entity, typically to discover or obtain something for that other entity’s benefit.
-
E.
usesExplorationMethod
chosen
Indicates that one entity employs or applies a particular exploration method as part of its process or behavior.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.