Triple
T32178702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US1011371077 |
E821924
|
entity |
| Predicate | isAssociatedWithIssuerIndustry |
P173827
|
FINISHED |
| Object | medical devices |
—
|
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: medical devices | Statement: [US1011371077, isAssociatedWithIssuerIndustry, medical devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssociatedWithIssuerIndustry Context triple: [US1011371077, isAssociatedWithIssuerIndustry, medical devices]
-
A.
acquirerIndustry
Indicates the industry or sector in which the acquiring entity in a transaction operates.
-
B.
associatedWithRoleOfIssuer
Indicates that one entity is connected to or involved in the capacity, function, or responsibilities of an issuer.
-
C.
isNonbankIssuer
Indicates that the subject issues financial instruments or payment products but is not a licensed or regulated bank.
-
D.
indicatesIssuer
Indicates that one entity serves as the issuer or originator of another entity, such as a document, credential, or financial instrument.
-
E.
typicalIssuer
Indicates that one entity is the standard or commonly expected issuer (e.g., of a document, instrument, or credential) for another entity.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba7b13b481908a3658adff04878c |
completed | May 3, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:34 a.m.