Triple
T264999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .NET Framework |
E5703
|
entity |
| Predicate | latestStableReleaseVersion |
P3698
|
FINISHED |
| Object | 4.8.1 |
—
|
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: 4.8.1 | Statement: [.NET Framework, latestStableReleaseVersion, 4.8.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latestStableReleaseVersion Context triple: [.NET Framework, latestStableReleaseVersion, 4.8.1]
-
A.
latestVersion
chosen
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
-
B.
releaseChannel
Indicates the distribution pathway or medium through which something (such as a product, update, or content) is made available or delivered to its recipients.
-
C.
isLastMajor
Indicates that an entity is the final or most recent significant item or event within a defined sequence or set.
-
D.
currentCoreVersionEnactedIn
Indicates that a specific version of the core (e.g., a standard, framework, or core specification) is currently in force within a given context, jurisdiction, or system.
-
E.
releaseType
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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25d8f9bbc8190a13841e4de093a66 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.