Triple
T25835763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southfork Ranch |
E650790
|
entity |
| Predicate | hasOnsiteDining |
P55802
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Southfork Ranch, hasOnsiteDining, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnsiteDining Context triple: [Southfork Ranch, hasOnsiteDining, true]
-
A.
hasDiningOptionType
Indicates that an entity offers or is associated with a specific type or category of dining option (e.g., dine-in, takeout, delivery).
-
B.
hasDiningFeature
chosen
Indicates that something possesses a specific characteristic, amenity, or attribute related to dining.
-
C.
isDiningDestination
Indicates that a place serves as a destination where people go specifically to eat meals or dine.
-
D.
hasCharacterDining
Indicates that an entity offers or includes dining experiences where guests can eat while interacting with costumed characters.
-
E.
hasDiningFocus
Indicates that an entity is primarily oriented toward or specialized in dining-related activities, services, or experiences.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 22, 2026, 7:41 a.m.