Triple
T29948873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyphomicrobiales |
E760715
|
entity |
| Predicate | containsPhotosyntheticMembers |
P198078
|
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: [Hyphomicrobiales, containsPhotosyntheticMembers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPhotosyntheticMembers Context triple: [Hyphomicrobiales, containsPhotosyntheticMembers, true]
-
A.
photosyntheticOrganism
Indicates that an organism performs photosynthesis, converting light energy into chemical energy to sustain itself.
-
B.
photosyntheticCapability
Indicates the ability of one entity to perform photosynthesis, converting light energy into chemical energy.
-
C.
photosyntheticOrgan
Indicates that an entity is an organ specialized for performing photosynthesis in an organism.
-
D.
photosyntheticTissue
Indicates that an entity has tissue capable of performing photosynthesis, converting light energy into chemical energy.
-
E.
photosyntheticApparatus
Indicates the relationship in which an entity possesses or is associated with a system of structures and molecules that carry out photosynthesis.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69fec8adaa308190a9a276f8c36f15f0 |
completed | May 9, 2026, 5:39 a.m. |
Created at: April 29, 2026, 6:25 p.m.