Triple
T37174205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSSC |
E920994
|
entity |
| Predicate | holeTransportLayer |
P187503
|
FINISHED |
| Object | liquid electrolyte |
—
|
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: liquid electrolyte | Statement: [DSSC, holeTransportLayer, liquid electrolyte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holeTransportLayer Context triple: [DSSC, holeTransportLayer, liquid electrolyte]
-
A.
transportLayerFor
Indicates that one entity functions as the transport-layer protocol or mechanism used to carry or deliver another entity’s data.
-
B.
physicalTunnel
Indicates that one entity is connected to another by a physical tunnel or passageway allowing movement or transfer between them.
-
C.
tunnelType
Indicates the specific kind or classification of a tunnel associated with an entity.
-
D.
tunnelsProtocol
Indicates that one communication protocol is encapsulated and transmitted within another protocol, creating a tunnel through the outer protocol’s channel.
-
E.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb55dc36d08190a0634fa680e13114 |
completed | May 6, 2026, 2:53 p.m. |
Created at: May 3, 2026, 4:15 p.m.