Triple
T27732719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.SByte |
E697467
|
entity |
| Predicate | languageAlias_VisualBasic |
P194066
|
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_VisualBasic, SByte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageAlias_VisualBasic Context triple: [System.SByte, languageAlias_VisualBasic, SByte]
-
A.
languageVariant
Indicates that one language is a variant, dialect, or localized form of another language.
-
B.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
C.
languageName
Indicates the specific name assigned to a language in the relationship.
-
D.
languageOfVariant
Indicates that one entity is the language in which a particular variant or version of another entity is expressed.
-
E.
workLanguageVariant
Indicates that one language variant of a work is related to another version of the same work, typically differing by language or localization.
- F. None of above. chosen
Provenance (4 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_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
| PDg | Predicate description generation | batch_69fd5f2903a48190ac4b718bff99c6cf |
completed | May 8, 2026, 3:57 a.m. |
Created at: April 27, 2026, 3:12 p.m.