Triple
T17253983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadlands geothermal field |
E418831
|
entity |
| Predicate | hasHostRocks |
P53497
|
FINISHED |
| Object | volcanic rocks |
—
|
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: volcanic rocks | Statement: [Broadlands geothermal field, hasHostRocks, volcanic rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostRocks Context triple: [Broadlands geothermal field, hasHostRocks, volcanic rocks]
-
A.
hostRock
chosen
Indicates that one rock body serves as the surrounding or enclosing rock in which another geological feature (such as an ore deposit, vein, or intrusion) occurs.
-
B.
hasHosts
Indicates that one entity serves as the host or hosting environment for another entity.
-
C.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
D.
supportsHostManagement
Indicates that an entity provides functionality to manage, configure, or control a host system or environment.
-
E.
hasSiblingHosts
Indicates that two or more entities share at least one common host, making them sibling hosts in relation to that shared hosting 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e6b2b1c8190b446ce648ecaad80 |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.