Triple
T10243792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GitHub Actions |
E183288
|
entity |
| Predicate | owner |
P347
|
FINISHED |
| Object | GitHub |
E5697
|
NE 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: GitHub | Statement: [GitHub Actions, owner, GitHub]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GitHub Context triple: [GitHub Actions, owner, GitHub]
-
A.
GitHub
chosen
GitHub is a widely used web-based platform for version control and collaborative software development, built around the Git system and popular among open-source and enterprise projects.
-
B.
GitLab
GitLab is a web-based DevOps platform that provides Git repository hosting along with integrated tools for source code management, CI/CD, and project collaboration.
-
C.
Bitbucket
Bitbucket is a web-based platform for hosting Git repositories that provides source code management, collaboration tools, and integration with development workflows.
-
D.
Git
Git is a widely used distributed version control system designed to efficiently track changes in source code and support collaborative software development.
-
E.
GitHub API v4
GitHub API v4 is GitHub’s GraphQL-based API that enables flexible, efficient querying and manipulation of GitHub data and resources.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d22a76188190a73df23bfb08eb3d |
completed | April 7, 2026, 9:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d71cb24d088190848d2fb1fffe4c48 |
completed | April 9, 2026, 3:27 a.m. |
Created at: April 6, 2026, 11:26 a.m.