Triple
T25919276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferrar Dolerite |
E653121
|
entity |
| Predicate | hostRocks |
P53497
|
FINISHED |
| Object | Beacon Supergroup |
—
|
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: Beacon Supergroup | Statement: [Ferrar Dolerite, hostRocks, Beacon Supergroup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostRocks Context triple: [Ferrar Dolerite, hostRocks, Beacon Supergroup]
-
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.
hostPark
Indicates that an entity provides space or facilities for a park to be located or held within its area.
-
C.
hostCraton
Indicates that one geological feature or unit is situated within or supported by a cratonic block (ancient, stable part of the continental lithosphere).
-
D.
hostArena
Indicates that one entity serves as the arena or venue where an event or activity involving the other entity takes place.
-
E.
hostRepublic
Indicates that an entity serves as the host country or republic for another entity or event.
- 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603e7c6ec8190afd0f94ebeb1c130 |
completed | May 2, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:31 a.m.