Triple
T25101766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursus americanus californiensis |
E628745
|
entity |
| Predicate | hasTrophicRole |
P116360
|
FINISHED |
| Object | seed disperser |
—
|
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: seed disperser | Statement: [Ursus americanus californiensis, hasTrophicRole, seed disperser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrophicRole Context triple: [Ursus americanus californiensis, hasTrophicRole, seed disperser]
-
A.
trophicType
Indicates the way an organism obtains its energy and nutrients within a food web or ecosystem.
-
B.
isMajorFoodSourceFor
Indicates that something serves as a primary or significant source of food for another entity.
-
C.
trophicLevel
Indicates the position an organism occupies in a food chain, based on how it obtains energy and nutrients (e.g., producer, primary consumer, top predator).
-
D.
hasPositionInDiet
Indicates the relative role or ranking that something occupies within a diet or dietary plan.
-
E.
ecologicalRoles
chosen
Indicates the various functional relationships or roles an entity plays within an ecosystem, such as its contributions to energy flow, nutrient cycling, or species interactions.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 18, 2026, 6:25 a.m.