Triple
T18091263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornubian Batholith |
E432971
|
entity |
| Predicate | outcropsAs |
P87992
|
FINISHED |
| Object | moorland tors |
—
|
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: moorland tors | Statement: [Cornubian Batholith, outcropsAs, moorland tors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcropsAs Context triple: [Cornubian Batholith, outcropsAs, moorland tors]
-
A.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
B.
shareGeologicalFeature
Indicates that two or more entities have a geological feature in common, such as sharing the same type, structure, or formation.
-
C.
commonRockUnit
Indicates that two or more geological features share the same rock unit or lithostratigraphic layer.
-
D.
notableQuarry
Indicates that an entity is a quarry that is particularly significant, well-known, or noteworthy in some context.
-
E.
associatedTopography
chosen
Indicates a relationship where one entity is linked or connected to a particular topographical feature or terrain.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd18b55081909c416fb7186bd4a4 |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.