Triple
T37017822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fingal Head |
E916130
|
entity |
| Predicate | geologyOrigin |
P6355
|
FINISHED |
| Object | Tweed Volcano |
—
|
NE NERFINISHED |
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: Tweed Volcano | Statement: [Fingal Head, geologyOrigin, Tweed Volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologyOrigin Context triple: [Fingal Head, geologyOrigin, Tweed Volcano]
-
A.
geologicalOriginRegion
Indicates the geographic region from which a geological feature, material, or formation originally derives.
-
B.
geologyRelatedTo
Indicates a relationship where one geological entity, feature, or concept is connected, associated, or relevant to another within the domain of geology.
-
C.
volcanicOrigin
chosen
Indicates that something originates from, is produced by, or is directly associated with volcanic activity or processes.
-
D.
geologyIncludes
Indicates that one geological entity contains, encompasses, or has as a component another geological entity.
-
E.
geologicalBranchOf
Indicates that one geological unit, feature, or formation is a subdivision or offshoot of a larger, parent geological entity within a hierarchical 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.