Triple
T24512108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomo cultural area |
E606252
|
entity |
| Predicate | includesEnvironmentType |
P13810
|
FINISHED |
| Object | river environments |
—
|
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: river environments | Statement: [Pomo cultural area, includesEnvironmentType, river environments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEnvironmentType Context triple: [Pomo cultural area, includesEnvironmentType, river environments]
-
A.
hasEnvironmentType
chosen
Indicates that an entity is associated with or occurs within a specific type or category of environment.
-
B.
isEnvironmentOf
Indicates that one entity serves as the surrounding conditions, context, or setting in which another entity exists, operates, or occurs.
-
C.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
D.
supportsEnvironment
Indicates that one entity provides the necessary conditions, compatibility, or resources for another entity to operate or exist within a particular environment.
-
E.
includesFeatureTypes
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
- 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:24 a.m.