Triple
T29689677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLAG Linux and GNU |
E751179
|
entity |
| Predicate | upstreamDistribution |
P114489
|
FINISHED |
| Object | Fedora Core |
—
|
NE NERFINISHED |
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: Fedora Core | Statement: [BLAG Linux and GNU, upstreamDistribution, Fedora Core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upstreamDistribution Context triple: [BLAG Linux and GNU, upstreamDistribution, Fedora Core]
-
A.
distributionFor
Indicates a relationship where one entity serves as the distribution, delivery, or dissemination mechanism for another entity.
-
B.
distributionVia
Indicates that something is delivered, supplied, or made available through a particular channel, medium, or intermediary.
-
C.
targetDistribution
Indicates the intended allocation or spread of something (such as resources, data, or outputs) across specified targets or recipients.
-
D.
distributedAs
Indicates that something is allocated, delivered, or spread out according to a particular pattern, rule, or distribution scheme.
-
E.
distributesFrom
chosen
Indicates that something acts as the source or origin from which items, resources, or information are distributed to others.
- 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:15 p.m.