Triple
T35411200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario College Graduate Certificate |
E1023515
|
entity |
| Predicate | typicalProviderType |
P86906
|
FINISHED |
| Object | public college |
—
|
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: public college | Statement: [Ontario College Graduate Certificate, typicalProviderType, public college]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProviderType Context triple: [Ontario College Graduate Certificate, typicalProviderType, public college]
-
A.
typicalProvider
Indicates that one entity commonly or characteristically serves as a provider of goods, services, or resources to another entity.
-
B.
providerOf
Indicates that one entity supplies, furnishes, or makes available a good, service, or resource to another entity.
-
C.
serviceProviderType
chosen
Indicates the category or kind of service provider associated with an entity or transaction.
-
D.
typicalTargetType
Indicates the usual or most common type or category of entity that serves as the target or recipient in a given relationship or action.
-
E.
typicalBureauType
Indicates that one entity is the standard or commonly occurring type or category of bureau associated with another entity.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.