Triple
T29689996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musix GNU+Linux (historical) |
E751186
|
entity |
| Predicate | isMaintained |
P52206
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Musix GNU+Linux (historical), isMaintained, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMaintained Context triple: [Musix GNU+Linux (historical), isMaintained, no]
-
A.
stillMaintained
chosen
Indicates that the subject continues to be actively maintained or supported over time.
-
B.
hasMaintained
Indicates that an entity has continued to keep another entity in a particular state, condition, or relationship over a period of time.
-
C.
hasMaintenance
Indicates that an entity is subject to, associated with, or requires a particular maintenance activity or maintenance record.
-
D.
canMaintain
Indicates that one entity has the ability or capacity to maintain, service, or keep another entity in proper working condition.
-
E.
oftenMaintainedBy
Indicates that something is regularly or frequently kept in working order, cared for, or updated by a particular agent or 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672938e18819082394196f97e6340 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 7:16 p.m.