Triple
T37871162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laguna Grande bioluminescent bay |
E944608
|
entity |
| Predicate | causeOfGlow |
P90712
|
FINISHED |
| Object | bioluminescent microorganisms |
—
|
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: bioluminescent microorganisms | Statement: [Laguna Grande bioluminescent bay, causeOfGlow, bioluminescent microorganisms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfGlow Context triple: [Laguna Grande bioluminescent bay, causeOfGlow, bioluminescent microorganisms]
-
A.
glows
Indicates that one entity emits a steady or radiant light that is perceptible to others.
-
B.
glowsInPresenceOf
Indicates that one entity emits or intensifies light when another specified entity or condition is present.
-
C.
bioluminescenceTriggeredBy
chosen
Indicates that an organism’s bioluminescent emission occurs as a result of a specified trigger or stimulus.
-
D.
usesBioluminescenceFor
Indicates that an entity employs bioluminescence specifically for a particular function, purpose, or context.
-
E.
hasPhosphorescence
Indicates that one entity exhibits phosphorescence as a property or characteristic.
- 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_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:19 p.m.