Triple
T36594298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SeeDB |
E902753
|
entity |
| Predicate | advantageOverSolventMethods |
P186058
|
FINISHED |
| Object | better preservation of fluorescence |
—
|
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: better preservation of fluorescence | Statement: [SeeDB, advantageOverSolventMethods, better preservation of fluorescence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advantageOverSolventMethods Context triple: [SeeDB, advantageOverSolventMethods, better preservation of fluorescence]
-
A.
typicalSolvent
Indicates that one entity is commonly or characteristically used as a solvent for the other entity.
-
B.
isMoreSolubleIn
Indicates that one substance has a greater tendency to dissolve in a specified solvent than another substance does.
-
C.
advantageOverConventionalAbrasives
Indicates that something possesses a performance or functional benefit when compared to conventional abrasives.
-
D.
isInsolubleIn
Indicates that one substance does not dissolve in another under specified conditions.
-
E.
separationMethod
Indicates the technique or process used to separate one substance, component, or entity from another.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.