Triple
T25872630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suilven |
E651799
|
entity |
| Predicate | geologicalBase |
P89872
|
FINISHED |
| Object | Lewisian gneiss |
—
|
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: Lewisian gneiss | Statement: [Suilven, geologicalBase, Lewisian gneiss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicalBase Context triple: [Suilven, geologicalBase, Lewisian gneiss]
-
A.
geologicalSystem
Indicates that one entity is a geological system (e.g., rock units, structures, or processes forming a coherent geologic framework) associated with or characterizing the other entity.
-
B.
geologicalCoreOf
Indicates that one entity is the central, innermost geological part or core of another geological structure or body.
-
C.
geologyRelatedTo
Indicates a relationship where one geological entity, feature, or concept is connected, associated, or relevant to another within the domain of geology.
-
D.
hasGeologicalNature
chosen
Indicates that something possesses a specific geological character, composition, or formation type.
-
E.
geologicalRole
Indicates the functional or classificatory role an entity plays within geological processes, structures, or contexts.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f602dd86dc8190b36335017d158398 |
completed | May 2, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:11 a.m.