Triple
T38637985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GitHub Student Developer Pack |
E937610
|
entity |
| Predicate | offersType |
P17471
|
FINISHED |
| Object | free access |
—
|
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: free access | Statement: [GitHub Student Developer Pack, offersType, free access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersType Context triple: [GitHub Student Developer Pack, offersType, free access]
-
A.
offersObject
Indicates that a subject provides or makes available a specific object to another party as an offer.
-
B.
offersServiceType
chosen
Indicates that one entity provides or makes available a specific type or category of service to another entity or the public.
-
C.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
-
D.
offersConfiguration
Indicates that one entity provides or makes available a specific configuration to another entity or for a particular purpose.
-
E.
offersForm
Indicates that one entity provides or makes available a specific form (e.g., a document or interface) for another entity to use or complete.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
Created at: May 3, 2026, 4:32 p.m.