Triple
T8682277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Void Linux |
E206064
|
entity |
| Predicate | hasSourceRepository |
P19959
|
FINISHED |
| Object | https://github.com/void-linux |
—
|
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: https://github.com/void-linux | Statement: [Void Linux, hasSourceRepository, https://github.com/void-linux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceRepository Context triple: [Void Linux, hasSourceRepository, https://github.com/void-linux]
-
A.
hasRepository
chosen
Indicates that an entity maintains or is associated with a specific repository (such as a code, data, or content store).
-
B.
hasRepositoryMirror
Indicates that one repository serves as a mirrored copy or synchronized duplicate of another repository.
-
C.
hasPackageRepository
Indicates that an entity is associated with or provides access to a specific software package repository.
-
D.
hasDefinitionSource
Indicates that the definition of an entity originates from or is documented in a specified source.
-
E.
hasSourceWork
Indicates that something originates from, is derived from, or is based on a particular source work.
- 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.