Triple
T29406414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fedora IoT |
E745786
|
entity |
| Predicate | editionStatus |
P158993
|
FINISHED |
| Object | official Fedora Edition |
—
|
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: official Fedora Edition | Statement: [Fedora IoT, editionStatus, official Fedora Edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editionStatus Context triple: [Fedora IoT, editionStatus, official Fedora Edition]
-
A.
printEditionStatus
chosen
Indicates whether a given item or work is currently available or designated as a print edition.
-
B.
edition
Indicates that one entity is a specific version, issue, or release of another (typically a work such as a book, journal, or software).
-
C.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
-
D.
editionPattern
Indicates a recurring structure or template that characterizes how different editions or versions of something are organized or produced.
-
E.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
- 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_69f66a336608819088fa6f60f21d1a87 |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:54 p.m.