Triple
T27615266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Dynamic Language Runtime team |
E700422
|
entity |
| Predicate | documentationPublishedOn |
P164511
|
FINISHED |
| Object | MSDN |
—
|
NE NERFINISHED |
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: MSDN | Statement: [Microsoft Dynamic Language Runtime team, documentationPublishedOn, MSDN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentationPublishedOn Context triple: [Microsoft Dynamic Language Runtime team, documentationPublishedOn, MSDN]
-
A.
documentTypePublished
Indicates that a specific type or category of document has been formally published or made publicly available.
-
B.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
C.
hasPublicationDate
Indicates that an entity is associated with the specific date on which it was published.
-
D.
finalPublicationDate
Indicates the date on which a work is officially and definitively published in its final form.
-
E.
documentationProvidedAt
Indicates that documentation is supplied, made available, or presented at a specific time, place, or context.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 2:12 p.m.