Triple
T28505695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lubuntu |
E721358
|
entity |
| Predicate | supportsInstallationFrom |
P31893
|
FINISHED |
| Object | live USB |
—
|
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: live USB | Statement: [Lubuntu, supportsInstallationFrom, live USB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInstallationFrom Context triple: [Lubuntu, supportsInstallationFrom, live USB]
-
A.
supportsInstallation
Indicates that one entity is capable of enabling, handling, or being compatible with the installation of another entity.
-
B.
requiresInstallation
Indicates that one entity must be installed or set up before the other can be used or become operational.
-
C.
includesInstallation
Indicates that one entity comes with or provides the installation of another entity as part of its offering or package.
-
D.
supportsInstallationMedia
chosen
Indicates that one entity is capable of accepting, handling, or working with a specified type of installation media for setup or deployment purposes.
-
E.
typeOfInstallationSupported
Indicates that one entity supports or is compatible with a specified type or method of installation for another entity.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00be8ee4bc8190b795d9606f0e490c |
completed | May 10, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_6a00bde163c88190867104bd08cac2ee |
completed | May 10, 2026, 5:18 p.m. |
Created at: April 28, 2026, 3:09 a.m.