Triple
T27732718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.SByte |
E697467
|
entity |
| Predicate | languageAlias_CSharp |
P193930
|
FINISHED |
| Object | sbyte |
—
|
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: sbyte | Statement: [System.SByte, languageAlias_CSharp, sbyte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageAlias_CSharp Context triple: [System.SByte, languageAlias_CSharp, sbyte]
-
A.
languageCSharpName
chosen
Indicates that the entity’s name is expressed using the C# programming language’s naming conventions or identifier format.
-
B.
languageName
Indicates the specific name assigned to a language in the relationship.
-
C.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
D.
languageCategory
Indicates the classification relationship where a language is assigned to a particular linguistic or functional category.
-
E.
languageSpecifies
Indicates that one entity defines or constrains the syntax, semantics, or usage rules that govern how another language or linguistic system is expressed or interpreted.
- 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_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 27, 2026, 3:12 p.m.