Triple
T29689780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperbola GNU/Linux-libre |
E751181
|
entity |
| Predicate | avoidsSaaSDependencies |
P167599
|
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, avoidsSaaSDependencies, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avoidsSaaSDependencies Context triple: [Hyperbola GNU/Linux-libre, avoidsSaaSDependencies, yes]
-
A.
usesCloudTechnologyFrom
Indicates that one entity employs or relies on cloud-based technology, services, or infrastructure provided by another entity.
-
B.
supportsDataCenterAbstraction
Indicates that one entity provides or enables an abstraction layer for representing or managing data center resources or functionality.
-
C.
hasInfrastructureScale
Indicates the relative size, capacity, or extent of infrastructure associated with or supporting an entity.
-
D.
usesServiceBasedArchitecture
Indicates that one entity designs or operates its system using a service-based architecture, where functionality is organized into distinct, interacting services.
-
E.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by 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_69f672938e18819082394196f97e6340 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 7:15 p.m.