Triple
T27750017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | git-scm.com |
E702090
|
entity |
| Predicate | licenseDocumentationFor |
P147731
|
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: [git-scm.com, licenseDocumentationFor, Git]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseDocumentationFor Context triple: [git-scm.com, licenseDocumentationFor, Git]
-
A.
licenseFor
Indicates that one entity grants or holds formal permission or authorization for another entity to perform an activity, use a resource, or operate under specified conditions.
-
B.
licenseOfProduct
Indicates that a specified license applies to, governs, or is associated with a particular product.
-
C.
legalLicenseIn
Indicates that an entity holds a valid legal license or authorization to operate, practice, or conduct a specified activity within a particular jurisdiction or region.
-
D.
licenseTextAvailableAt
chosen
Indicates that the full text of a license can be accessed or retrieved at a specified location or resource.
-
E.
licenseFocus
Indicates that a license specifically targets, applies to, or is primarily concerned with a particular subject, activity, or scope.
- 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_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 4:19 p.m.