Triple
T27666964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dotnet/sdk |
E697250
|
entity |
| Predicate | tagPrefix |
P162931
|
FINISHED |
| Object | mcr.microsoft.com/dotnet/sdk |
—
|
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: mcr.microsoft.com/dotnet/sdk | Statement: [dotnet/sdk, tagPrefix, mcr.microsoft.com/dotnet/sdk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tagPrefix Context triple: [dotnet/sdk, tagPrefix, mcr.microsoft.com/dotnet/sdk]
-
A.
namespacePrefix
Indicates the abbreviated prefix string associated with a particular namespace URI in a naming or identifier system.
-
B.
namePrefix
Indicates that one entity is a prefix or leading part of another entity’s name.
-
C.
registrationPrefix
Indicates that an entity has a specific registration prefix code assigned to it as part of its official registration or identification.
-
D.
regionPrefix
Indicates that one region’s identifier or code serves as the starting substring (prefix) of another region’s identifier or code, expressing a hierarchical or nested regional relationship.
-
E.
tagType
Indicates the classification or category assigned to a tag, specifying what kind of tag it is or how it should be interpreted.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f634a50f3481908954bd4b691d6f19 |
completed | May 2, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f6305219f08190b55f6193a4a49984 |
completed | May 2, 2026, 5:11 p.m. |
Created at: April 27, 2026, 2:39 p.m.