Triple
T28608893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kernel.org |
E724122
|
entity |
| Predicate | versionControlSystemUsed |
P9403
|
FINISHED |
| Object | Git |
—
|
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 | Statement: [kernel.org, versionControlSystemUsed, Git]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: versionControlSystemUsed Context triple: [kernel.org, versionControlSystemUsed, Git]
-
A.
usesVersionControlSystem
chosen
Indicates that an entity employs a version control system to manage and track changes to its files or code.
-
B.
previouslySupportedVersionControlSystem
Indicates that an entity used to support a particular version control system in the past but no longer does so.
-
C.
versionControlledBy
Indicates that an item (such as a file, document, or resource) is managed and tracked under the change history of a specific version control system or repository.
-
D.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to another entity.
-
E.
versionComponent
Indicates that one entity is a component or segment of another entity’s version identifier (e.g., major, minor, or patch number).
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:29 a.m.