Triple
T32378234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GTK# |
E827343
|
entity |
| Predicate | supportsGTKVersion |
P55140
|
FINISHED |
| Object | GTK 2 |
E203866
|
NE 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: GTK 2 | Statement: [GTK#, supportsGTKVersion, GTK 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGTKVersion Context triple: [GTK#, supportsGTKVersion, GTK 2]
-
A.
supportsSinceVersion
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
-
B.
supportsSince
Indicates that one entity has been providing support to another entity starting from a specific point in time and continuing thereafter.
-
C.
supportsSpecificationVersion
chosen
Indicates that one entity is compatible with and able to operate according to a particular version of a specification.
-
D.
supportsKubernetesVersion
Indicates that one entity is compatible with and able to run or work correctly with a specified Kubernetes version.
-
E.
supportsGraphicalUserInterface
Indicates that an entity is capable of operating with or providing a graphical user interface for interaction.
- F. None of above.
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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a33e8b7e1308190934a7a5a17e8ef42 |
completed | June 18, 2026, 12:46 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:51 a.m.