Triple
T1612494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Entity Framework |
E34642
|
entity |
| Predicate | repositoryURL |
P6055
|
FINISHED |
| Object | https://github.com/dotnet/ef6 |
—
|
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/dotnet/ef6 | Statement: [Entity Framework, repositoryURL, https://github.com/dotnet/ef6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repositoryURL Context triple: [Entity Framework, repositoryURL, https://github.com/dotnet/ef6]
-
A.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
B.
openSourceProject
Indicates that the subject is a software project whose source code is publicly available and can be used, modified, and redistributed under an open-source license.
-
C.
accessURL
chosen
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
D.
githubUsername
Indicates that one entity is the GitHub account username associated with another entity.
-
E.
hasRepositoryMirror
Indicates that one repository serves as a mirrored copy or synchronized duplicate of another repository.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.