Triple

T19383804
Position Surface form Disambiguated ID Type / Status
Subject Quest University Canada E484877 entity
Predicate hadResidentialRequirement P14094 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: [Quest University Canada, hadResidentialRequirement, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadResidentialRequirement
Context triple: [Quest University Canada, hadResidentialRequirement, yes]
  • A. hasResidentialRequirement chosen
    Indicates that an entity is subject to a condition requiring residence in a specified place or under specified living arrangements.
  • B. requiredAcceptanceOfResidentOf
    Indicates that one party must obtain the approval or consent of a specified resident before proceeding with an action or arrangement.
  • C. densityRequirement
    Indicates that there is a specified minimum or target density that must be met or maintained in the relationship between the related entities.
  • D. grantedResidence
    Indicates that one entity has officially conferred the right to reside or live in a place or jurisdiction to another entity.
  • E. locationRequirement
    Indicates that a specific location or type of place is required or must be satisfied for an action, condition, or relationship to hold.
  • 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.