Triple
T37449596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Photobacterium phosphoreum |
E930640
|
entity |
| Predicate | lightRegulation |
P40123
|
FINISHED |
| Object | quorum-sensing controlled bioluminescence |
—
|
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: quorum-sensing controlled bioluminescence | Statement: [Photobacterium phosphoreum, lightRegulation, quorum-sensing controlled bioluminescence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightRegulation Context triple: [Photobacterium phosphoreum, lightRegulation, quorum-sensing controlled bioluminescence]
-
A.
lightPeriod
Indicates the duration or interval during which light is present or active in a given context.
-
B.
lightType
Indicates the specific category or kind of light associated with an entity or lighting setup.
-
C.
lightOrganFunction
Indicates that one entity serves as the functional light-producing organ or structure for another entity.
-
D.
lightRange
Indicates the distance or area over which a light source effectively emits or illuminates.
-
E.
lightingControlledBy
chosen
Indicates that the lighting system or device is operated, regulated, or influenced by a specified controller or control mechanism.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.