Triple
T33901014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porichthys notatus |
E869046
|
entity |
| Predicate | photophoreLocation |
P93327
|
FINISHED |
| Object | ventral surface |
—
|
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: ventral surface | Statement: [Porichthys notatus, photophoreLocation, ventral surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: photophoreLocation Context triple: [Porichthys notatus, photophoreLocation, ventral surface]
-
A.
lightOrganLocation
chosen
Indicates the anatomical location or placement of a light-producing organ within or on an organism.
-
B.
bioluminescenceSource
Indicates that one entity is the origin or producer of the bioluminescent light exhibited by another entity.
-
C.
hasPhosphorescence
Indicates that one entity exhibits phosphorescence as a property or characteristic.
-
D.
usesBioluminescenceFor
Indicates that an entity employs bioluminescence specifically for a particular function, purpose, or context.
-
E.
positionOnSubstance
Indicates that one entity is located on the surface of, or supported by, another entity that is treated as a substance or material.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.