Triple

T25506825
Position Surface form Disambiguated ID Type / Status
Subject Hisar Kampüsü E639265 entity
Predicate hasUsers P158607 FINISHED
Object ziyaretçiler 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: ziyaretçiler | Statement: [Hisar Kampüsü, hasUsers, ziyaretçiler]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUsers
Context triple: [Hisar Kampüsü, hasUsers, ziyaretçiler]
  • A. hasUsers chosen
    Indicates that an entity is associated with one or more users who use, own, or are linked to it.
  • B. hasUser
    Indicates that an entity is associated with or linked to a specific user.
  • C. hasUserService
    Indicates that an entity is associated with or utilizes a particular user-related service.
  • D. hasProductUser
    Indicates that a product is associated with or used by a particular user.
  • E. hasSecondaryUser
    Indicates that an entity is associated with an additional, non-primary user who also has access to or control over it.
  • 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_69e75dbd09308190b6b5f0afdc12ec6d completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f806927881908443eaf9584c11b1 completed May 2, 2026, 1:11 p.m.
PD Predicate disambiguation batch_69f4a0f7c6008190ae8cee3e71e19b94 completed May 1, 2026, 12:47 p.m.
Created at: April 21, 2026, 2:47 p.m.