Triple
T28610032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multipass |
E724146
|
entity |
| Predicate | supportsImage |
P203254
|
FINISHED |
| Object | Ubuntu LTS releases |
—
|
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: Ubuntu LTS releases | Statement: [Multipass, supportsImage, Ubuntu LTS releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsImage Context triple: [Multipass, supportsImage, Ubuntu LTS releases]
-
A.
supportsJPEG
Indicates that one entity is capable of handling, displaying, or processing JPEG image files for another entity or in a given context.
-
B.
containsImage
Indicates that one entity includes or embeds an image as part of its content or structure.
-
C.
hasImageFeature
Indicates that an entity is associated with a specific visual characteristic or attribute extracted from an image.
-
D.
supportsHEIF
Indicates that one entity provides compatibility with or the ability to handle HEIF (High Efficiency Image File) format for another entity.
-
E.
isImageOf
Indicates that one entity is a visual depiction or representation of another entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a0143a4ab3c8190a240b0facfe130a9 |
completed | May 11, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_6a01426b2d4481908654bfa4a02c457d |
completed | May 11, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_6a0143a400f881909599405b47dc1c78 |
completed | May 11, 2026, 2:49 a.m. |
Created at: April 28, 2026, 4:29 a.m.