Triple
T27750006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | git-scm.com |
E702090
|
entity |
| Predicate | softwareDownloadFor |
P90390
|
FINISHED |
| Object | Git for 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: Git for Linux | Statement: [git-scm.com, softwareDownloadFor, Git for Linux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareDownloadFor Context triple: [git-scm.com, softwareDownloadFor, Git for Linux]
-
A.
softwareFor
Indicates that one entity is designed, intended, or used to operate on, support, or be compatible with another entity as software.
-
B.
softwareLibrary
Indicates that one entity is a software library that provides code, functionality, or services used by another entity.
-
C.
softwareName
Indicates that one entity is the name or title of a software application associated with another entity.
-
D.
downloadFrom
chosen
Indicates that a file, data, or resource is transferred and obtained from a specified source or provider.
-
E.
softwareFormat
Indicates that one entity specifies or uses the file or data format in which a software-related item is encoded, stored, or delivered.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 4:19 p.m.