Triple
T19383816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quest University Canada |
E484877
|
entity |
| Predicate | hadCampus |
P26464
|
FINISHED |
| Object | purpose-built campus in Squamish |
—
|
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: purpose-built campus in Squamish | Statement: [Quest University Canada, hadCampus, purpose-built campus in Squamish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCampus Context triple: [Quest University Canada, hadCampus, purpose-built campus in Squamish]
-
A.
hostsCampusOf
Indicates that one entity serves as the physical location or site where another entity’s campus is situated or maintained.
-
B.
hasCampusOn
chosen
Indicates that an institution or organization maintains a campus located on a specified geographic area or site.
-
C.
campus
Indicates that an entity is located on, associated with, or taking place within a particular campus.
-
D.
cityCampus
Indicates that a campus is located within or associated with a particular city.
-
E.
campus1
Indicates a relationship where an entity is identified as a campus or is located on/associated with a particular campus.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a626b288190a27a30deb0ccabc3 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.