Triple
T27142340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Céide Fields |
E681846
|
entity |
| Predicate | hasCurrentEnvironment |
P2936
|
FINISHED |
| Object | peat-covered plateau |
—
|
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: peat-covered plateau | Statement: [Céide Fields, hasCurrentEnvironment, peat-covered plateau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentEnvironment Context triple: [Céide Fields, hasCurrentEnvironment, peat-covered plateau]
-
A.
hasEnvironmentType
Indicates that an entity is associated with or occurs within a specific type or category of environment.
-
B.
hasPrimaryEnvironment
Indicates that an entity is associated with its main or most characteristic environment or setting.
-
C.
hasCurrent
chosen
Indicates that an entity presently possesses, exhibits, or is associated with a particular state, attribute, or resource at the current time.
-
D.
hasApproachEnvironment
Indicates that an entity uses, is associated with, or is designed for a particular environment or context in which it operates or approaches something.
-
E.
hasGeneralEnvironment
Indicates that an entity exists or operates within a broad or overall environmental context or setting.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 27, 2026, 9:10 a.m.