Triple
T18419404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cmd/compile |
E441981
|
entity |
| Predicate | supportsGoVersion |
P55177
|
FINISHED |
| Object | Go 1.x series |
—
|
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: Go 1.x series | Statement: [cmd/compile, supportsGoVersion, Go 1.x series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGoVersion Context triple: [cmd/compile, supportsGoVersion, Go 1.x series]
-
A.
supportsSinceVersion
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
-
B.
supportsLanguageVersion
chosen
Indicates that one entity provides compatibility with, or can correctly operate using, a specified version of a language.
-
C.
supportsSpecificationVersion
Indicates that one entity is compatible with and able to operate according to a particular version of a specification.
-
D.
supportsSemanticVersioning
Indicates that one entity adheres to and correctly handles semantic versioning rules for another entity’s versions.
-
E.
supportsVendor
Indicates that one entity provides assistance, resources, or endorsement to a vendor in carrying out its activities or services.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a2a0fb08190b409ed200a9d86a6 |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.