Triple
T32378336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .NET generics |
E827345
|
entity |
| Predicate | syntaxExampleLanguage |
P168241
|
FINISHED |
| Object | C# |
—
|
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: C# | Statement: [.NET generics, syntaxExampleLanguage, C#]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: syntaxExampleLanguage Context triple: [.NET generics, syntaxExampleLanguage, C#]
-
A.
codeExample
Indicates that one entity provides a snippet or sample of source code that illustrates how to use, implement, or demonstrate another entity.
-
B.
codeLanguage
chosen
Indicates that one entity is expressed, written, or implemented using the programming or markup language specified by the other entity.
-
C.
languageFeature
Indicates that one entity is a characteristic, property, or capability of a language associated with the other entity.
-
D.
syntaxBasedOn
Indicates that the syntactic structure or rules of one entity are derived from, influenced by, or constructed according to the syntax of another entity.
-
E.
languageOfCode
Indicates that a programming code artifact is written in, or uses, a particular programming language.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c13307548190b3e209bff21ab524 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:51 a.m.