Triple
T37449583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Photobacterium phosphoreum |
E930640
|
entity |
| Predicate | lightOrganAssociation |
P188322
|
FINISHED |
| Object | fish light organs |
—
|
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: fish light organs | Statement: [Photobacterium phosphoreum, lightOrganAssociation, fish light organs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightOrganAssociation Context triple: [Photobacterium phosphoreum, lightOrganAssociation, fish light organs]
-
A.
lightOrganFunction
Indicates that one entity serves as the functional light-producing organ or structure for another entity.
-
B.
lightOrganLocation
Indicates the anatomical location or placement of a light-producing organ within or on an organism.
-
C.
lightDistribution
Indicates how light is spatially distributed or spread from a source across a given area or environment.
-
D.
lightType
Indicates the specific category or kind of light associated with an entity or lighting setup.
-
E.
featuresLightingBy
Indicates that something includes or showcases lighting created, provided, or designed by a specified entity.
- F. None of above. chosen
Provenance (4 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.