Triple
T36571444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | atmospheric pressure chemical ionization |
E902131
|
entity |
| Predicate | transferToMassAnalyzer |
P57570
|
FINISHED |
| Object | sampling orifice |
—
|
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: sampling orifice | Statement: [atmospheric pressure chemical ionization, transferToMassAnalyzer, sampling orifice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferToMassAnalyzer Context triple: [atmospheric pressure chemical ionization, transferToMassAnalyzer, sampling orifice]
-
A.
transferDestination
chosen
Indicates the entity that serves as the receiving end or target location of a transfer from another entity.
-
B.
transferMode
Indicates the method or mechanism by which something is transferred from one entity to another.
-
C.
transferPathwayTo
Indicates the act of moving or reassigning a pathway (such as a process, route, or channel) from one entity to another.
-
D.
transferSystem
Indicates a relationship where something is moved, conveyed, or reassigned from one entity or location to another within a defined system or process.
-
E.
transferAfter
Indicates that one entity transfers something to another entity only after a specified event or condition has occurred.
- F. None of above.
Provenance (3 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: May 3, 2026, 4:11 p.m.