Triple
T29689770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperbola GNU/Linux-libre |
E751181
|
entity |
| Predicate | removesTrackingFeatures |
P169323
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hyperbola GNU/Linux-libre, removesTrackingFeatures, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removesTrackingFeatures Context triple: [Hyperbola GNU/Linux-libre, removesTrackingFeatures, yes]
-
A.
trimFeatures
Indicates that certain features or attributes of an entity are reduced, removed, or cut down, typically to simplify or optimize it.
-
B.
featureRemoved
Indicates that a previously existing feature has been taken out, disabled, or is no longer available.
-
C.
removedAthleticsTrack
Indicates that an athletics track previously present at a location or facility has been taken away or dismantled.
-
D.
trackFeature
Indicates that one entity monitors, records, or follows the behavior, state, or evolution of a particular feature associated with another entity.
-
E.
removesDRMRelatedComponents
Indicates that an entity eliminates or strips out components associated with digital rights management (DRM) from 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67de7792c81909b5e4e812d143624 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 28, 2026, 7:15 p.m.