Triple
T18487184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Industrial Research Chairs |
E451719
|
entity |
| Predicate | researchSetting |
P5064
|
FINISHED |
| Object | Canadian universities |
—
|
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: Canadian universities | Statement: [Industrial Research Chairs, researchSetting, Canadian universities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchSetting Context triple: [Industrial Research Chairs, researchSetting, Canadian universities]
-
A.
researchMode
Indicates that an entity is engaged in or configured for conducting systematic investigation, experimentation, or study.
-
B.
researchValue
Indicates that something is considered useful, important, or relevant for research or scholarly investigation.
-
C.
researchContext
chosen
Indicates the situational, methodological, or thematic setting within which a particular piece of research is conducted or interpreted.
-
D.
researchComponent
Indicates that an entity functions as a part or element within a broader research activity, project, or study.
-
E.
researchArm
Indicates that an entity is a specific study group or treatment arm within a research or clinical trial design.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d7e79c819083bf5c54faaa4810 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.