Triple
T20922634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ExCeL London |
E515252
|
entity |
| Predicate | hasHallCount |
P2490
|
FINISHED |
| Object | 6 main exhibition halls |
—
|
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: 6 main exhibition halls | Statement: [ExCeL London, hasHallCount, 6 main exhibition halls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHallCount Context triple: [ExCeL London, hasHallCount, 6 main exhibition halls]
-
A.
numberOfHalls
chosen
Indicates the quantity of halls associated with a given entity or location.
-
B.
hasSingleHall
Indicates that an entity possesses exactly one hall within its structure or domain.
-
C.
hasStationHall
Indicates that one entity (typically a station) includes or is associated with a station hall area as part of its structure or facilities.
-
D.
hasSmallHallCapacity
Indicates that the capacity of a hall is below a defined threshold, classifying it as small.
-
E.
hasSecondaryHallCapacity
Indicates that an entity possesses a specified capacity for a secondary hall or auxiliary event space.
- 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.