Triple
T27732702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.SByte |
E697467
|
entity |
| Predicate | underlyingFramework |
P2450
|
FINISHED |
| Object | .NET |
—
|
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 | Statement: [System.SByte, underlyingFramework, .NET]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingFramework Context triple: [System.SByte, underlyingFramework, .NET]
-
A.
parentFramework
Indicates that one framework serves as the higher-level or containing framework from which another framework is derived, organized, or structured.
-
B.
currentFrameworkBasedOn
chosen
Indicates that the current framework is derived from, built upon, or structured according to another underlying framework.
-
C.
frameworkFor
Indicates that one entity serves as a supporting structure, system, or basis that organizes, guides, or enables the development or functioning of another entity.
-
D.
frameworkSupport
Indicates that one entity provides compatibility with, or operational support for, a particular framework used by another entity.
-
E.
frameworkName
Indicates that a specific framework is identified by the given name.
- 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_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 3:12 p.m.