Triple
T27731577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NUnit.Framework.TestAttribute |
E697441
|
entity |
| Predicate | hasTargetFramework |
P30253
|
FINISHED |
| Object | .NET Framework |
—
|
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: .NET Framework | Statement: [NUnit.Framework.TestAttribute, hasTargetFramework, .NET Framework]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetFramework Context triple: [NUnit.Framework.TestAttribute, hasTargetFramework, .NET Framework]
-
A.
supportsTargetFrameworkMonikers
chosen
Indicates that an entity is compatible with, or can operate under, one or more specified target framework monikers (TFMs).
-
B.
hasTargetPlatform
Indicates that something is intended to run on, be compatible with, or be deployed to a specified platform.
-
C.
currentFrameworkBasedOn
Indicates that the current framework is derived from, built upon, or structured according to another underlying framework.
-
D.
hasFrameworkInstrument
Indicates that one entity uses or is associated with a specific framework as the instrument or means for performing an action or achieving a result.
-
E.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 3:11 p.m.