Triple
T29438295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRBP |
E746639
|
entity |
| Predicate | typeOfEcosystems |
P168853
|
FINISHED |
| Object | riparian ecosystems |
—
|
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: riparian ecosystems | Statement: [NRBP, typeOfEcosystems, riparian ecosystems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEcosystems Context triple: [NRBP, typeOfEcosystems, riparian ecosystems]
-
A.
ecosystemRepresentation
Indicates that one entity serves as a model, depiction, or abstraction of an ecosystem, capturing its components, structure, or dynamics.
-
B.
ecosystemTerm
chosen
Indicates that one entity is a term, label, or concept used within the context of an ecosystem or ecological system.
-
C.
ecoregionsInclude
Indicates that one ecoregion spatially contains or encompasses another ecoregion or area within its boundaries.
-
D.
ecosystemRelevance
Indicates the degree to which something is important, impactful, or integral to the functioning or health of a particular ecosystem.
-
E.
ecoregion
Indicates that one entity is located within, associated with, or belongs to the same ecological region as another entity.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: April 28, 2026, 3:19 p.m.