Triple

T1624089
Position Surface form Disambiguated ID Type / Status
Subject The Midland Bar E35097 entity
Predicate targetClientele P481 FINISHED
Object hotel guests 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: hotel guests | Statement: [The Midland Bar, targetClientele, hotel guests]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: targetClientele
Context triple: [The Midland Bar, targetClientele, hotel guests]
  • A. targetMarket chosen
    Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
  • B. targetsGroup
    Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
  • C. target
    Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
  • D. targetedPopulation
    Indicates the group of individuals or entities that an action, intervention, or effect is specifically directed toward.
  • E. targetStudentGroup
    Indicates a relationship where something is directed, tailored, or intended specifically for a particular group of students.
  • 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_69a886023194819080a3fccd6e325d0e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aaf4a0ef748190ae52b9656474c0ef completed March 6, 2026, 3:37 p.m.
PD Predicate disambiguation batch_69a907c731808190a1d998155041b3c1 completed March 5, 2026, 4:34 a.m.
Created at: March 4, 2026, 7:28 p.m.