Triple
T6376650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faculty of Mathematics, University of Waterloo |
E143482
|
entity |
| Predicate | hasCoop |
P33628
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Faculty of Mathematics, University of Waterloo, hasCoop, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoop Context triple: [Faculty of Mathematics, University of Waterloo, hasCoop, yes]
-
A.
hasCooperative
Indicates that one entity participates in a cooperative relationship or partnership with another entity.
-
B.
hasCoopPrograms
chosen
Indicates that an entity offers or participates in cooperative education programs in partnership with other organizations or institutions.
-
C.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
D.
cooperationPartner
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
-
E.
cooperationType
Indicates the specific kind or form of cooperative relationship that exists between the related entities.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0683d7af881908d66d5230e1bfcb6 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.