Triple
T37871163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laguna Grande bioluminescent bay |
E944608
|
entity |
| Predicate | dominantOrganism |
P38050
|
FINISHED |
| Object | dinoflagellates |
—
|
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: dinoflagellates | Statement: [Laguna Grande bioluminescent bay, dominantOrganism, dinoflagellates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantOrganism Context triple: [Laguna Grande bioluminescent bay, dominantOrganism, dinoflagellates]
-
A.
dominantLifeformType
Indicates which type of lifeform holds primary dominance or control within a given context or environment.
-
B.
hasDominantSpecies
chosen
Indicates that one entity possesses or is characterized by a species that is predominant or most influential within it.
-
C.
dominantCommunity
Indicates that one community holds a prevailing or controlling influence, status, or presence over others within a given context.
-
D.
organismType
Indicates the biological classification or kind of organism that an entity is.
-
E.
targetOrganism
Indicates that an action, process, or effect is directed toward or intended to impact a particular organism.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:19 p.m.