Triple
T32415001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azure Artifacts |
E828313
|
entity |
| Predicate | supportsPackageType |
P44388
|
FINISHED |
| Object | NuGet |
E34611
|
NE 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: NuGet | Statement: [Azure Artifacts, supportsPackageType, NuGet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPackageType Context triple: [Azure Artifacts, supportsPackageType, NuGet]
-
A.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
B.
hasPackageType
chosen
Indicates that an entity is associated with or classified under a particular type or category of package.
-
C.
supportsProgramType
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
-
D.
supportsPluginType
Indicates that one entity is capable of working with, handling, or being compatible with a specified type of plugin.
-
E.
supportsProjectType
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
- F. None of above.
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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a344f221f6481908c40eae36a406f3f |
completed | June 18, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:53 a.m.