Triple
T27945877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NetBIOS API |
E700876
|
entity |
| Predicate | associatedWithVendor |
P74056
|
FINISHED |
| Object | IBM |
—
|
NE NERFINISHED |
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: IBM | Statement: [NetBIOS API, associatedWithVendor, IBM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithVendor Context triple: [NetBIOS API, associatedWithVendor, IBM]
-
A.
associatedWithVendorProgram
Indicates that an entity has a formal relationship or participation connection with a specific vendor’s program.
-
B.
usedByVendor
Indicates that something (such as a product, tool, or resource) is utilized or employed by a vendor.
-
C.
associatedWithProvider
chosen
Indicates that one entity has a connection or relationship with a specific provider, such as being supplied, managed, or serviced by that provider.
-
D.
associatedWithCustom
Indicates a relationship where one entity is linked to or connected with another entity in a non-standard, user-defined, or customized manner.
-
E.
eligibleVendors
Indicates that certain vendors meet the required criteria or conditions to be considered eligible for a specified purpose or process.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a008d6085508190a71c52cd028a6297 |
completed | May 10, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a008ced31448190b8fc60bf87b40647 |
completed | May 10, 2026, 1:49 p.m. |
Created at: April 27, 2026, 7:22 p.m.