Triple
T33197918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biltmore Hotels |
E849815
|
entity |
| Predicate | typicalGuestUse |
P43099
|
FINISHED |
| Object | social events |
—
|
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: social events | Statement: [Biltmore Hotels, typicalGuestUse, social events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGuestUse Context triple: [Biltmore Hotels, typicalGuestUse, social events]
-
A.
typicalGuests
Indicates the usual or most common guests associated with a particular host, place, or event.
-
B.
typicalGuestConfederation
Indicates that one entity is typically a guest or participant within the confederation represented by the other entity.
-
C.
typicalInteraction
Indicates the usual or most common way in which two entities interact or relate to each other.
-
D.
visitorUse
chosen
Indicates that an entity is being used, accessed, or engaged with by a visitor or temporary user.
-
E.
intendedGuest
Indicates that one entity is designated or planned to be a guest of another entity or event.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:29 a.m.