Triple
T28368875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timmins campus |
E718568
|
entity |
| Predicate | academicLanguage |
P164432
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [Timmins campus, academicLanguage, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: academicLanguage Context triple: [Timmins campus, academicLanguage, French]
-
A.
academicContext
Indicates the educational or scholarly setting, framework, or circumstances within which an activity, relationship, or piece of information takes place.
-
B.
academicUse
Indicates that something is intended for, suitable for, or used within an academic or educational context.
-
C.
academicEmphasis
Indicates a focus or concentration of study or specialization within an academic program or curriculum.
-
D.
academicAccess
Indicates that one entity has permission or the ability to use, enter, or benefit from academic resources, environments, or services provided by another entity.
-
E.
academicAudience
Indicates that something is intended for, directed toward, or primarily relevant to an academic or scholarly audience.
- F. None of above. chosen
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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c582da481909a86d6f72b452ad7 |
completed | May 2, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f64bca8574819095e081cbb7e2f369 |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 28, 2026, 12:57 a.m.