Triple
T6332469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch of Isbister |
E142412
|
entity |
| Predicate | isNatural |
P58243
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Loch of Isbister, isNatural, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNatural Context triple: [Loch of Isbister, isNatural, true]
-
A.
hasNature
Indicates that something possesses, exhibits, or is characterized by a particular inherent quality, essence, or fundamental type.
-
B.
isNaturalFeature
chosen
Indicates that the subject is a naturally occurring physical feature of the environment, not created or significantly altered by human activity.
-
C.
naturalOrArtificial
Indicates that something is classified as either naturally occurring or artificially created.
-
D.
isNaturalFiber
Indicates that a material or textile is made from fibers derived from natural sources rather than synthetic ones.
-
E.
hasNaturalSignificance
Indicates that something possesses inherent meaning, importance, or value derived from its nature or from natural properties, rather than from convention or assignment.
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651634b08190b54860ba0a70f5c4 |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.