Triple
T9255051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clupea |
E222418
|
entity |
| Predicate | importanceInFoodWeb |
P65595
|
FINISHED |
| Object | key prey for larger fish |
—
|
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: key prey for larger fish | Statement: [Clupea, importanceInFoodWeb, key prey for larger fish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importanceInFoodWeb Context triple: [Clupea, importanceInFoodWeb, key prey for larger fish]
-
A.
trophicType
Indicates the way an organism obtains its energy and nutrients within a food web or ecosystem.
-
B.
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).
-
C.
hasEconomicImportanceFor
Indicates that one entity holds economic value, benefit, or significance for another entity.
-
D.
notableSpeciesRole
Indicates that a species plays a particularly important, characteristic, or influential role in relation to another entity or context.
-
E.
ecologicalRelevance
chosen
Indicates that one entity has significance, impact, or importance for the functioning, stability, or dynamics of another entity’s ecosystem or ecological context.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b3c314819096632b8263288aae |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:31 p.m.