Triple
T9214245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyrobaculum aerophilum |
E221201
|
entity |
| Predicate | electronDonor |
P86890
|
FINISHED |
| Object | hydrogen |
—
|
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: hydrogen | Statement: [Pyrobaculum aerophilum, electronDonor, hydrogen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electronDonor Context triple: [Pyrobaculum aerophilum, electronDonor, hydrogen]
-
A.
isDonorProgramOf
Indicates that one entity is a donor program that provides funding or resources to support another entity.
-
B.
donated
Indicates that one entity voluntarily gave something of value (such as money, goods, or time) to another entity, typically without expecting anything in return.
-
C.
electrodeType
Indicates the specific kind or classification of an electrode associated with an entity or used in a given context.
-
D.
electrolyte
Indicates a relationship where a substance functions as an electrolyte for another entity, typically by enabling or supporting ionic conduction in that context.
-
E.
hasElectronConfiguration
Indicates that an entity (typically an atom or ion) possesses a specific arrangement of electrons in its atomic orbitals.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda06bf80819094c6e74b4b6a31e4 |
completed | April 1, 2026, 8:40 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc687067fc81909da2d78fda0cdcfb |
completed | April 1, 2026, 12:36 a.m. |
Created at: March 30, 2026, 7:27 p.m.