Triple
T36934406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NMR spectroscopy |
E913571
|
entity |
| Predicate | requiresSampleForm |
P201687
|
FINISHED |
| Object | solution |
—
|
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: solution | Statement: [NMR spectroscopy, requiresSampleForm, solution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSampleForm Context triple: [NMR spectroscopy, requiresSampleForm, solution]
-
A.
requiresPetitionForm
Indicates that performing this action or establishing this relationship is contingent upon the submission or completion of a petition form.
-
B.
supportsForm
Indicates that one entity provides compatibility or backing for a particular form, format, or type associated with another entity.
-
C.
supportsForms
Indicates that one entity is capable of handling, accepting, or working with specific forms or form types associated with another entity.
-
D.
usesForm
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
-
E.
hasOnlineForm
Indicates that an entity provides or is associated with a form that can be accessed and completed online.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
| PDg | Predicate description generation | batch_6a001440a26c81908ba50779bb6e1679 |
completed | May 10, 2026, 5:14 a.m. |
Created at: May 3, 2026, 4:13 p.m.