Triple
T37535715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aliivibrio fischeri |
E933189
|
entity |
| Predicate | usesQuorumSensing |
P188212
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aliivibrio fischeri, usesQuorumSensing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesQuorumSensing Context triple: [Aliivibrio fischeri, usesQuorumSensing, true]
-
A.
secretedInResponseTo
Indicates that a substance is released or discharged as a direct reaction to a specific stimulus, condition, or event.
-
B.
biofilmFormation
Indicates the process or capability of forming a biofilm, where microorganisms adhere to a surface and to each other within a protective matrix.
-
C.
sporeFormation
Indicates the process by which an organism produces and releases spores as a means of reproduction, survival, or dispersal.
-
D.
usesBioluminescenceFor
Indicates that an entity employs bioluminescence specifically for a particular function, purpose, or context.
-
E.
isSymbiotic
Indicates a mutually dependent relationship in which two entities interact in ways that benefit at least one and typically support the survival or well-being of both.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.