Triple

T14313273
Position Surface form Disambiguated ID Type / Status
Subject The Mall at Rockingham Park E354887 entity
Predicate hasDiningOptionType P113735 FINISHED
Object fast food restaurants 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: fast food restaurants | Statement: [The Mall at Rockingham Park, hasDiningOptionType, fast food restaurants]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDiningOptionType
Context triple: [The Mall at Rockingham Park, hasDiningOptionType, fast food restaurants]
  • A. hasDiningFeature
    Indicates that something possesses a specific characteristic, amenity, or attribute related to dining.
  • B. hasDiningPolicy
    Indicates that an entity enforces or follows a specific set of rules or guidelines related to dining or meal-related activities.
  • C. hasCharacterDining
    Indicates that an entity offers or includes dining experiences where guests can eat while interacting with costumed characters.
  • D. isDiningDestination
    Indicates that a place serves as a destination where people go specifically to eat meals or dine.
  • E. hasDishType
    Indicates that an item (such as a food or menu entry) is classified as belonging to a particular type of dish (e.g., appetizer, main course, dessert).
  • F. None of above. chosen

Provenance (4 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_69d8278ed42c8190b9f882dcce611347 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de85b49e5481909b9ffab2d922e284 completed April 14, 2026, 6:21 p.m.
PD Predicate disambiguation batch_69de2a8f81f08190af737e1654847aa6 completed April 14, 2026, 11:52 a.m.
PDg Predicate description generation batch_69de2e07d1f88190bdcd20967e484718 completed April 14, 2026, 12:07 p.m.
Created at: April 10, 2026, 1:12 a.m.