Triple
T29689909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLAG (historical) |
E751184
|
entity |
| Predicate | removedNonFreeComponentsFromUpstream |
P168773
|
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: [BLAG (historical), removedNonFreeComponentsFromUpstream, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removedNonFreeComponentsFromUpstream Context triple: [BLAG (historical), removedNonFreeComponentsFromUpstream, yes]
-
A.
removesFromUpstream
Indicates that one entity eliminates or detaches another entity from an upstream source or dependency in a process or flow.
-
B.
removesDRMRelatedComponents
chosen
Indicates that an entity eliminates or strips out components associated with digital rights management (DRM) from another entity.
-
C.
featureRemoved
Indicates that a previously existing feature has been taken out, disabled, or is no longer available.
-
D.
replacesComponentOf
Indicates that one entity takes the place of a specific component within another entity, substituting for that component in its role or function.
-
E.
cannotBeUninstalled
Indicates that the specified entity cannot be removed or uninstalled from the system or environment.
- 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_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 7:16 p.m.