Triple

T36931464
Position Surface form Disambiguated ID Type / Status
Subject Hampton Place E913489 entity
Predicate targetResidentGroup P134232 FINISHED
Object UBC faculty and staff 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: UBC faculty and staff | Statement: [Hampton Place, targetResidentGroup, UBC faculty and staff]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: targetResidentGroup
Context triple: [Hampton Place, targetResidentGroup, UBC faculty and staff]
  • A. residenceGroup chosen
    Indicates that multiple entities share a common place of residence or are grouped together based on living at the same location.
  • B. targetsGroup
    Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
  • C. nativeGroupOf
    Indicates that one entity is the indigenous or original ethnic group associated with, originating from, or traditionally inhabiting the other entity (such as a place or region).
  • D. representedGroups
    Indicates that an entity serves as an official or recognized representative for one or more groups.
  • E. participantGroup
    Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
  • 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_69f76e896c988190880c130e01303dd4 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69ff1f3f94fc819095955299f50ab4ce completed May 9, 2026, 11:49 a.m.
PD Predicate disambiguation batch_69ff1ea47748819082f63d9b9d9c3e65 completed May 9, 2026, 11:46 a.m.
Created at: May 3, 2026, 4:13 p.m.