Triple
T34640026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ossiriand (partly) |
E889529
|
entity |
| Predicate | typeOfEnvironment |
P13810
|
FINISHED |
| Object | riverine woodland |
—
|
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: riverine woodland | Statement: [Ossiriand (partly), typeOfEnvironment, riverine woodland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEnvironment Context triple: [Ossiriand (partly), typeOfEnvironment, riverine woodland]
-
A.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
B.
environmentClass
Indicates that an entity belongs to, or is categorized within, a particular type or class of environment.
-
C.
hasEnvironmentType
chosen
Indicates that an entity is associated with or occurs within a specific type or category of environment.
-
D.
launchEnvironment
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
E.
isEnvironmentOf
Indicates that one entity serves as the surrounding conditions, context, or setting in which another entity exists, operates, or occurs.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a014f7602988190b8f86cb431a9cf12 |
completed | May 11, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_6a014a70ea748190bd86fb9f218103ba |
completed | May 11, 2026, 3:18 a.m. |
Created at: May 1, 2026, 2:04 a.m.