Triple
T38131597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AACD–Servidor station |
E952235
|
entity |
| Predicate | ticketingAreaLocation |
P43373
|
FINISHED |
| Object | concourse level |
—
|
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: concourse level | Statement: [AACD–Servidor station, ticketingAreaLocation, concourse level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketingAreaLocation Context triple: [AACD–Servidor station, ticketingAreaLocation, concourse level]
-
A.
ticketingLocation
chosen
Indicates the place or point where tickets are issued, sold, or otherwise processed for an event, service, or journey.
-
B.
ticketSalesArea
Indicates the geographic or market area within which tickets are sold or valid for a particular event, service, or provider.
-
C.
ticketAcceptanceArea
Indicates the geographic or operational area within which a given ticket is valid for use or accepted as proof of payment.
-
D.
ticketingContext
Indicates the situational or operational context in which a ticket (such as a support, event, or issue ticket) is created, managed, or applied.
-
E.
ticketZoneSystem
Indicates that there is a specific fare or access zoning system governing how tickets are defined, priced, or validated within a transport or event context.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.