Triple
T27755761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPersistStorage |
E701328
|
entity |
| Predicate | binaryCompatibility |
P4635
|
FINISHED |
| Object | standard COM vtable layout |
—
|
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: standard COM vtable layout | Statement: [IPersistStorage, binaryCompatibility, standard COM vtable layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: binaryCompatibility Context triple: [IPersistStorage, binaryCompatibility, standard COM vtable layout]
-
A.
backwardCompatibility
Indicates that one entity remains functional or compatible when used with an earlier version or older form of another entity.
-
B.
backwardCompatibleWith
chosen
Indicates that one entity can correctly interpret, use, or function with data, interfaces, or behavior designed for an earlier version of another entity.
-
C.
checksCompatibilityWith
Indicates that one entity evaluates whether it is compatible or can function harmoniously with another entity.
-
D.
requiresCompatibilityWith
Indicates that one entity can only function correctly or be used if it is compatible with another specified entity.
-
E.
compatibilityGoal
Indicates that one entity has an objective or intended outcome related to being compatible or achieving compatibility with 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_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 4:23 p.m.