Triple
T1718155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XFS |
E37333
|
entity |
| Predicate | releasedOnLinux |
P31911
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [XFS, releasedOnLinux, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedOnLinux Context triple: [XFS, releasedOnLinux, 2001]
-
A.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
-
B.
releasedDuring
Indicates that one entity was released within the time period defined by another entity.
-
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.
releaseChannel
Indicates the distribution pathway or medium through which something (such as a product, update, or content) is made available or delivered to its recipients.
-
E.
usedByOperatingSystems
Indicates that something (such as a component, standard, or feature) is utilized or supported by one or more operating systems.
- F. None of above. chosen
Provenance (4 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab5c96db6c8190a745d6fef7bf2cdb |
completed | March 6, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69aa61bed2fc819086d912cd34285978 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab5c7780bc81909fc6e173a216cb0b |
completed | March 6, 2026, 11 p.m. |
Created at: March 4, 2026, 7:30 p.m.