Triple

T29534217
Position Surface form Disambiguated ID Type / Status
Subject Alba E749290 entity
Predicate hasSignificantLocation P177153 FINISHED
Object hotel room in Rome 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 room in Rome | Statement: [Alba, hasSignificantLocation, hotel room in Rome]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSignificantLocation
Context triple: [Alba, hasSignificantLocation, hotel room in Rome]
  • A. hasMajorLocation
    Indicates that an entity is primarily situated in, based in, or most significantly associated with a particular location.
  • B. hasProminentLocation
    Indicates that an entity occupies a highly visible, central, or otherwise notable position within a given space or context.
  • C. hasLocationRole
    Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
  • D. hasImportantLocality chosen
    Indicates that something possesses or is associated with a locality (place or region) that is considered significant or particularly relevant in the given context.
  • E. hasLocationComponent
    Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
  • 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_69f0bd47abb081909bd6e6a33d770fd8 completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f78c61ed4c8190ad84c918fa9af55a completed May 3, 2026, 5:56 p.m.
PD Predicate disambiguation batch_69f78b8cb3a881909ebaac1b503988c2 completed May 3, 2026, 5:53 p.m.
Created at: April 28, 2026, 4:56 p.m.