Triple

T3986666
Position Surface form Disambiguated ID Type / Status
Subject Atakule E86887 entity
Predicate revolvingRestaurantRotationPeriod P38870 FINISHED
Object 1 hour 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: 1 hour | Statement: [Atakule, revolvingRestaurantRotationPeriod, 1 hour]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: revolvingRestaurantRotationPeriod
Context triple: [Atakule, revolvingRestaurantRotationPeriod, 1 hour]
  • A. restaurantRotationPeriod
    Indicates the length of time it takes for a restaurant’s offerings, such as menus or featured items, to complete one full cycle before repeating.
  • B. hasRevolvingRestaurant
    Indicates that one entity features or contains a restaurant that rotates around a central axis, typically providing a 360-degree view.
  • C. rotationPeriod_hours chosen
    Indicates the length of time, measured in hours, that an object takes to complete one full rotation on its axis.
  • D. rotatesAmong
    Indicates that an entity takes turns occupying or performing a role, position, or function in sequence with other entities.
  • E. rotatesWith
    Indicates that two or more entities turn or spin together in a coordinated or mechanically linked manner, typically sharing the same rotational motion or axis.
  • 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_69aed93fd9d4819085d3b2137d2346cb completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefb81040481909b22e4c445ecae0f completed March 9, 2026, 4:55 p.m.
PD Predicate disambiguation batch_69aef8f692008190bf4d637ffc3d3eaa completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:33 p.m.