Triple
T22800736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scavaig River |
E564381
|
entity |
| Predicate | terminatesInEcosystem |
P149762
|
FINISHED |
| Object | marine |
—
|
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: marine | Statement: [Scavaig River, terminatesInEcosystem, marine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminatesInEcosystem Context triple: [Scavaig River, terminatesInEcosystem, marine]
-
A.
isWithinEcosystem
Indicates that one entity is located inside, and functionally part of, the ecological system defined by another entity.
-
B.
containsEcosystem
Indicates that one entity encompasses or includes an ecosystem within its boundaries or scope.
-
C.
operatesInEcosystem
Indicates that an entity functions, behaves, or carries out its activities within a particular ecosystem or environmental context.
-
D.
supportsEcosystemType
Indicates that one entity provides suitable conditions or resources necessary to sustain or maintain a particular type of ecosystem.
-
E.
terminatesFor
Indicates that one entity causes or marks the ending or cessation of another entity, process, or state.
- F. None of above. chosen
Provenance (4 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cdc72908190827c9e36a498dc97 |
completed | April 29, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:31 p.m.