Triple
T29689765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperbola GNU/Linux-libre |
E751181
|
entity |
| Predicate | providesHardenedConfigurations |
P100695
|
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, providesHardenedConfigurations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesHardenedConfigurations Context triple: [Hyperbola GNU/Linux-libre, providesHardenedConfigurations, yes]
-
A.
hasSafetyConfiguration
Indicates that an entity is associated with or assigned a particular safety-related setup, parameters, or protective settings.
-
B.
hardeningProperty
chosen
Indicates a relationship where one entity confers, causes, or characterizes the hardening behavior or hardening characteristics of another entity.
-
C.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
D.
requiresConfiguration
Indicates that one entity depends on another to be set up or configured before it can function or be used.
-
E.
numberOfConfigurations
Indicates the total count of distinct configurations associated with or applicable to a given entity or situation.
- 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_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 28, 2026, 7:15 p.m.