Triple
T27755518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IUnknown |
E701323
|
entity |
| Predicate | isFundamentalInterfaceFor |
P2421
|
FINISHED |
| Object | all COM interfaces |
—
|
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: all COM interfaces | Statement: [IUnknown, isFundamentalInterfaceFor, all COM interfaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFundamentalInterfaceFor Context triple: [IUnknown, isFundamentalInterfaceFor, all COM interfaces]
-
A.
isFundamental
Indicates that something is a basic, essential, or foundational element upon which other things depend or are built.
-
B.
isBaseFor
chosen
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
-
C.
isImplementationOf
Indicates that one entity realizes, fulfills, or concretely carries out the specification, interface, or abstract definition provided by another entity.
-
D.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
E.
followsInterfacesOf
Indicates that one entity adheres to or implements the interfaces defined or used by another entity.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63760b350819088f0eca0257ca125 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:23 p.m.