Triple
T1330362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AutoSyringe, Inc. |
E28627
|
entity |
| Predicate | roleInField |
P8439
|
FINISHED |
| Object | pioneer in portable infusion pumps |
—
|
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: pioneer in portable infusion pumps | Statement: [AutoSyringe, Inc., roleInField, pioneer in portable infusion pumps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInField Context triple: [AutoSyringe, Inc., roleInField, pioneer in portable infusion pumps]
-
A.
roleInIndustry
chosen
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
B.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
C.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
D.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
E.
roleSimilarTo
Indicates that two entities have roles or functions that are alike or closely comparable in nature or responsibility.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c449bc8190acb6603a0ddac7fd |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.