Triple
T29182964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilisk II |
E739791
|
entity |
| Predicate | supportsHostPlatform |
P5090
|
FINISHED |
| Object | Linux |
E5903
|
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: Linux | Statement: [Basilisk II, supportsHostPlatform, Linux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHostPlatform Context triple: [Basilisk II, supportsHostPlatform, Linux]
-
A.
supportsHostType
Indicates that one entity is capable of operating with, accommodating, or being compatible with a specified host type.
-
B.
supportedPlatform
chosen
Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
-
C.
supportsGuestArchitecture
Indicates that one entity provides the necessary capabilities or environment to run or host the specified guest architecture of another entity.
-
D.
unsupportedPlatform
Indicates that a given platform is not supported for a particular action, feature, or system.
-
E.
supportedSystem
Indicates that one entity provides compatibility, functionality, or operational support for another system.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a03142a3a7081909bcfb683b44e2217 |
completed | May 12, 2026, 11:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25507e14ec8190a44cacebe8b20ac7 |
completed | June 7, 2026, 11:05 a.m. |
| PD | Predicate disambiguation | batch_6a031400af808190a72abf095e96c151 |
completed | May 12, 2026, 11:50 a.m. |
Created at: April 28, 2026, 11:58 a.m.