Triple
T16864727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rannoch Moor crossing |
E410008
|
entity |
| Predicate | constructionChallenge |
P12940
|
FINISHED |
| Object | soft peat ground |
—
|
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: soft peat ground | Statement: [Rannoch Moor crossing, constructionChallenge, soft peat ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionChallenge Context triple: [Rannoch Moor crossing, constructionChallenge, soft peat ground]
-
A.
constructionChallenges
chosen
Indicates difficulties, obstacles, or complications encountered during the process of constructing or building something.
-
B.
designChallenge
Indicates a situation in which an entity is tasked with creating, improving, or solving something through a structured design problem or assignment.
-
C.
towerConstruction
Indicates the process or activity of building or erecting a tower structure.
-
D.
reconstructionChallenge
Indicates a situation where accurately rebuilding or restoring something from incomplete, damaged, or complex information is difficult or problematic.
-
E.
constructionBase
Indicates that one entity serves as the foundational structure or base upon which another entity is constructed or built.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b506dd1c81909ab8006b6a1e2b7a |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.