Triple
T32858650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beringer Vineyards |
E840447
|
entity |
| Predicate | RhineHouseFunction |
P175080
|
FINISHED |
| Object | hospitality center |
—
|
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: hospitality center | Statement: [Beringer Vineyards, RhineHouseFunction, hospitality center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RhineHouseFunction Context triple: [Beringer Vineyards, RhineHouseFunction, hospitality center]
-
A.
houseFunction
Indicates the functional role or primary use that a house serves (e.g., residential, commercial, mixed-use).
-
B.
heightAboveRhine
Indicates the vertical elevation of an entity relative to the water level of the Rhine River.
-
C.
ElizasHouseFunction
Indicates that something serves as the functional role, purpose, or use of Eliza’s house.
-
D.
hasRickhouses
Indicates that one entity possesses, contains, or is associated with one or more rickhouses used for storing aging barrels.
-
E.
RomanHouseFunction
Indicates the functional role or primary use assigned to a Roman house within its social, economic, or architectural context.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ceb2b81c81909c1a186305a9d597 |
completed | May 3, 2026, 4:27 a.m. |
| PD | Predicate disambiguation | batch_69f6cc177b288190904f3f23cb856d8b |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cdf2745481908464aa322c30d5b0 |
completed | May 3, 2026, 4:24 a.m. |
Created at: May 1, 2026, 1:17 a.m.