Triple
T5678650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglerfish |
E125146
|
entity |
| Predicate | escaFunction |
P16263
|
FINISHED |
| Object | emits light via bioluminescent bacteria |
—
|
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: emits light via bioluminescent bacteria | Statement: [Anglerfish, escaFunction, emits light via bioluminescent bacteria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escaFunction Context triple: [Anglerfish, escaFunction, emits light via bioluminescent bacteria]
-
A.
eraCode
Indicates the specific historical or temporal era associated with an entity, typically encoded as a standardized era identifier.
-
B.
escapeStatus
Indicates whether an entity has escaped, is in the process of escaping, or has not escaped from a given situation or confinement.
-
C.
evaluationFunction
Indicates a relationship where a specific procedure or rule assigns a value or score to an input, typically to assess its quality, utility, or desirability.
-
D.
eraInterpreted
Indicates that one entity has been interpreted, understood, or given meaning by another entity.
-
E.
exercisesFunction
chosen
Indicates that one entity performs or carries out the function, role, or capability associated with another entity.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.