Triple
T31505988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audioriver Festival |
E803817
|
entity |
| Predicate | hasAccommodationOption |
P17960
|
FINISHED |
| Object | festival campsite |
—
|
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: festival campsite | Statement: [Audioriver Festival, hasAccommodationOption, festival campsite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccommodationOption Context triple: [Audioriver Festival, hasAccommodationOption, festival campsite]
-
A.
hasAccommodation
chosen
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
B.
hasLodgeType
Indicates that an entity is associated with or classified by a particular type or category of lodge.
-
C.
hasCampingOption
Indicates that an entity offers or includes the possibility to camp (e.g., designated camping facilities or areas).
-
D.
hasAccommodationAtEndpoints
Indicates that the endpoints of something (e.g., a route, connection, or segment) each have available accommodation facilities.
-
E.
hasHotelType
Indicates that a hotel is classified as belonging to a specific type or category (e.g., resort, boutique, hostel).
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 30, 2026, 9:47 p.m.