Triple
T27737671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Runtime.Loader.AssemblyLoadContext |
E697567
|
entity |
| Predicate | hasVirtualMethod |
P173226
|
FINISHED |
| Object | Load(AssemblyName) |
—
|
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: Load(AssemblyName) | Statement: [System.Runtime.Loader.AssemblyLoadContext, hasVirtualMethod, Load(AssemblyName)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVirtualMethod Context triple: [System.Runtime.Loader.AssemblyLoadContext, hasVirtualMethod, Load(AssemblyName)]
-
A.
hasVirtualMachine
Indicates that one entity possesses, contains, or is associated with a virtual machine instance.
-
B.
hasMethodType
Indicates that an entity is associated with, or characterized by, a specific type or category of method used or applied in its context.
-
C.
hasPrototype
Indicates that an entity is based on, derived from, or exemplified by a specific prototype.
-
D.
hasClassMethod
Indicates that a class defines or contains a specific method as part of its behavior or interface.
-
E.
hasMethodCount
Indicates that an entity is associated with a specific number of methods it contains or defines.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 27, 2026, 3:13 p.m.