Triple
T6817380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aucilla River |
E156800
|
entity |
| Predicate | hasAdjacentEcosystem |
P64234
|
FINISHED |
| Object | wetlands |
—
|
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: wetlands | Statement: [Aucilla River, hasAdjacentEcosystem, wetlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentEcosystem Context triple: [Aucilla River, hasAdjacentEcosystem, wetlands]
-
A.
hasNearbyHabitats
chosen
Indicates that one entity has other habitats located close to it in geographic or spatial terms.
-
B.
containsEcosystem
Indicates that one entity encompasses or includes an ecosystem within its boundaries or scope.
-
C.
hasEcology
Indicates that an entity has a particular ecological context, such as its habitat, environmental role, or interactions within an ecosystem.
-
D.
partOfEcosystem
Indicates that an entity functions as a component within a larger ecological system, contributing to and affected by its interactions and processes.
-
E.
hasEcosystemService
Indicates that one entity provides, supports, or is associated with an ecosystem service that benefits another entity or the environment.
- 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_69c688298a288190af3f285d57f76bbe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:17 p.m.