Triple
T8681834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linux-libre |
E206055
|
entity |
| Predicate | isReleasedAs |
P42704
|
FINISHED |
| Object | source code tarballs |
—
|
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: source code tarballs | Statement: [Linux-libre, isReleasedAs, source code tarballs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReleasedAs Context triple: [Linux-libre, isReleasedAs, source code tarballs]
-
A.
fullyReleasedAs
Indicates that something has been completely made available or published in its final, unrestricted form.
-
B.
alsoReleased
Indicates that two or more items were released at the same time or as part of the same release event.
-
C.
releasedBy
Indicates that something (such as a product, work, or item) is made available, issued, or launched by a particular agent or organization.
-
D.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
E.
releasedAsPartOf
chosen
Indicates that one entity was issued, launched, or made available as a component or subset of a larger release, collection, or package represented by another entity.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae82e508190b0243328e98fcb1d |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.