Triple
T1611205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GitHub Copilot |
E34616
|
entity |
| Predicate | releasedAs |
P3286
|
FINISHED |
| Object | technical preview |
—
|
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: technical preview | Statement: [GitHub Copilot, releasedAs, technical preview]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedAs Context triple: [GitHub Copilot, releasedAs, technical preview]
-
A.
releasedDuring
Indicates that one entity was released within the time period defined by another entity.
-
B.
releasedFor
Indicates that something has been made available or authorized for public use, distribution, or access.
-
C.
releasedBy
Indicates that something (such as a product, work, or item) is made available, issued, or launched by a particular agent or organization.
-
D.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
-
E.
releaseType
chosen
Indicates the kind or category of a release event or version associated with an 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.