Triple
T12314354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maida Vale |
E293561
|
entity |
| Predicate | hasTicketHallDesign |
P104406
|
FINISHED |
| Object | red brick surface building |
—
|
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: red brick surface building | Statement: [Maida Vale, hasTicketHallDesign, red brick surface building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketHallDesign Context triple: [Maida Vale, hasTicketHallDesign, red brick surface building]
-
A.
hasTicketHall
Indicates that a place or facility includes or is equipped with a designated ticket hall area for purchasing or validating tickets.
-
B.
hasAuditorium
Indicates that one entity possesses or includes an auditorium as part of its facilities.
-
C.
hasConventionHalls
Indicates that an entity possesses or includes one or more convention halls as part of its facilities or infrastructure.
-
D.
hasSingleHall
Indicates that an entity possesses exactly one hall within its structure or domain.
-
E.
hasTicketBooths
Indicates that one entity possesses or contains ticket booths used for selling or distributing tickets.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:53 p.m.