Triple
T34955839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forge |
E1008120
|
entity |
| Predicate | supportsHostingService |
P29803
|
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: [Forge, supportsHostingService, GitHub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHostingService Context triple: [Forge, supportsHostingService, GitHub]
-
A.
supportsHosting
chosen
Indicates that one entity provides the necessary resources or capabilities for another entity to host or run something (such as an application, service, or content).
-
B.
supportsUserServices
Indicates that one entity provides the necessary functionality or resources for user-facing services to operate or be delivered.
-
C.
supportsProvider
Indicates that one entity provides assistance, resources, or endorsement to another entity acting in a provider role.
-
D.
supportsHostManagement
Indicates that an entity provides functionality to manage, configure, or control a host system or environment.
-
E.
supportsInfrastructure
Indicates that one entity provides resources, services, or capabilities that enable the operation, maintenance, or development of another entity’s infrastructure.
- F. None of above.
Provenance (4 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37a8ce4e0881909578bc67acb0ef51 |
completed | June 21, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.