Triple
T11096011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drakesbad Guest Ranch |
E262380
|
entity |
| Predicate | hasDiningPlan |
P47336
|
FINISHED |
| Object | American plan (meals included with lodging) |
—
|
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: American plan (meals included with lodging) | Statement: [Drakesbad Guest Ranch, hasDiningPlan, American plan (meals included with lodging)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiningPlan Context triple: [Drakesbad Guest Ranch, hasDiningPlan, American plan (meals included with lodging)]
-
A.
diningPlanEligible
Indicates that an entity qualifies for or is allowed to participate in a specified dining plan.
-
B.
diningPlanParticipation
Indicates that an entity is enrolled in or makes use of a specified dining plan.
-
C.
diningPlanCategory
chosen
Indicates the classification or type of dining plan associated with an entity, such as a person, reservation, or accommodation.
-
D.
hasDiningPolicy
Indicates that an entity enforces or follows a specific set of rules or guidelines related to dining or meal-related activities.
-
E.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0897188190b6c293b44990b3d4 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.