Triple
T2869222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Street Kensington Underground station |
E63516
|
entity |
| Predicate | hasTicketBarrier |
P43416
|
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: [High Street Kensington Underground station, hasTicketBarrier, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketBarrier Context triple: [High Street Kensington Underground station, hasTicketBarrier, yes]
-
A.
hasTicketRequirement
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
-
B.
hasTicketInspection
Indicates that a ticket is checked or verified by an authorized inspector or system.
-
C.
hasTicketHall
Indicates that a place or facility includes or is equipped with a designated ticket hall area for purchasing or validating tickets.
-
D.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
E.
hasTicketCollectorArea
Indicates that a location or facility includes a designated area where ticket collectors operate or perform their duties.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfe15ff081908dd1dad62c292b2b |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:02 p.m.