Triple
T17519385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encode OSS |
E426646
|
entity |
| Predicate | githubRepository |
P89567
|
FINISHED |
| Object | https://github.com/encode |
—
|
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/encode | Statement: [Encode OSS, githubRepository, https://github.com/encode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: githubRepository Context triple: [Encode OSS, githubRepository, https://github.com/encode]
-
A.
repositoryUrl
chosen
Indicates the web address where the related code, data, or resources are stored and managed in a version-controlled repository.
-
B.
repositoryName
Indicates the name assigned to a specific repository within a version control or storage system.
-
C.
githubOrganization
Indicates that an entity is an organization hosted on or associated with the GitHub platform.
-
D.
codeHostingService
Indicates a relationship where a platform provides hosting and management services for source code repositories and related development workflows.
-
E.
repositoryBrowser
Indicates a tool or interface that allows users to view, navigate, and explore the contents of a 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d18c1c81908bb843bbddb44ca1 |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.