Triple
T8288362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comdlg32 |
E193834
|
entity |
| Predicate | loadedAs |
P41759
|
FINISHED |
| Object | DLL |
—
|
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: DLL | Statement: [Comdlg32, loadedAs, DLL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadedAs Context triple: [Comdlg32, loadedAs, DLL]
-
A.
canBeLoadedAt
Indicates that an entity is capable of being placed onto or into another entity (such as a vehicle, container, or system) at a specific location or point in time.
-
B.
loadingMechanism
Indicates the method or system by which something is loaded into or onto another object or structure.
-
C.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
D.
loadType
chosen
Indicates the manner or category of how something is loaded, such as the method, configuration, or type of loading applied in a given context.
-
E.
loadBearingFor
Indicates that one entity structurally supports and carries the weight or load of 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c98e15c8190ac2a0b2a5ff834c9 |
completed | March 31, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:52 p.m.