Triple
T20922604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ExCeL London |
E515252
|
entity |
| Predicate | hasOnsiteHotels |
P84196
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ExCeL London, hasOnsiteHotels, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnsiteHotels Context triple: [ExCeL London, hasOnsiteHotels, yes]
-
A.
hasHotelsOnSite
chosen
Indicates that the subject location includes one or more hotels situated directly on its premises.
-
B.
hasResortHotel
Indicates that one entity owns, includes, or is associated with a resort hotel as part of its facilities or offerings.
-
C.
hasHotelType
Indicates that a hotel is classified as belonging to a specific type or category (e.g., resort, boutique, hostel).
-
D.
hasMountainHotel
Indicates that a location or region contains or is associated with a hotel situated in a mountainous area.
-
E.
hasOnsiteFeature
Indicates that one entity possesses or includes a particular feature that is physically present at its location or premises.
- 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f64f767481909deccd77b50bf4ae |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.