Triple
T31887194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DMLC |
E814036
|
entity |
| Predicate | codeHostedOn |
P55144
|
FINISHED |
| Object | GitHub |
—
|
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: GitHub | Statement: [DMLC, codeHostedOn, GitHub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeHostedOn Context triple: [DMLC, codeHostedOn, GitHub]
-
A.
codeHostingService
chosen
Indicates a relationship where a platform provides hosting and management services for source code repositories and related development workflows.
-
B.
hostedOn
Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
-
C.
repositoryUrl
Indicates the web address where the related code, data, or resources are stored and managed in a version-controlled repository.
-
D.
codeSpace
Indicates the namespace or contextual scope within which a piece of code, identifier, or programming element is defined and interpreted.
-
E.
repositoryName
Indicates the name assigned to a specific repository within a version control or storage system.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0e999888190b9dd00c81f5df261 |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:57 p.m.