Triple
T34667080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labridae |
E890284
|
entity |
| Predicate | hasRoleInEcosystem |
P3571
|
FINISHED |
| Object | coral reef cleaner fishes |
—
|
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: coral reef cleaner fishes | Statement: [Labridae, hasRoleInEcosystem, coral reef cleaner fishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInEcosystem Context triple: [Labridae, hasRoleInEcosystem, coral reef cleaner fishes]
-
A.
isWithinEcosystem
Indicates that one entity is located inside, and functionally part of, the ecological system defined by another entity.
-
B.
roleInEcosystem
chosen
Indicates the specific function or contribution an entity has within an ecosystem and how it interacts with other components of that system.
-
C.
containsEcosystem
Indicates that one entity encompasses or includes an ecosystem within its boundaries or scope.
-
D.
hasEcosystemService
Indicates that one entity provides, supports, or is associated with an ecosystem service that benefits another entity or the environment.
-
E.
statusInEcosystem
Indicates the role or position an entity holds within an ecosystem, such as its function, influence, or level in ecological hierarchies.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: May 1, 2026, 2:05 a.m.