Triple
T29406399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fedora IoT |
E745786
|
entity |
| Predicate | baseDistribution |
P173698
|
FINISHED |
| Object | Fedora Linux |
—
|
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 Linux | Statement: [Fedora IoT, baseDistribution, Fedora Linux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseDistribution Context triple: [Fedora IoT, baseDistribution, Fedora Linux]
-
A.
distributionBase
Indicates the primary location or facility from which something is distributed or supplied to other places.
-
B.
parentDistribution
chosen
Indicates that one entity serves as the source or upstream provider from which another entity’s distribution is derived or based.
-
C.
distributionFor
Indicates a relationship where one entity serves as the distribution, delivery, or dissemination mechanism for another entity.
-
D.
targetDistribution
Indicates the intended allocation or spread of something (such as resources, data, or outputs) across specified targets or recipients.
-
E.
distributionBy
Indicates how something is allocated, arranged, or spread according to a specified criterion or grouping.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 28, 2026, 2:54 p.m.