Triple
T34467949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Carmel |
E884824
|
entity |
| Predicate | ticketBarrierLocation |
P107454
|
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: [El Carmel, ticketBarrierLocation, concourse level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketBarrierLocation Context triple: [El Carmel, ticketBarrierLocation, concourse level]
-
A.
ticketingLocation
Indicates the place or point where tickets are issued, sold, or otherwise processed for an event, service, or journey.
-
B.
ticketAcceptanceArea
Indicates the geographic or operational area within which a given ticket is valid for use or accepted as proof of payment.
-
C.
hasTicketGatesLocation
chosen
Indicates that a place or facility has ticket gates located at or within a specified location.
-
D.
hasTicketBarrier
Indicates that an access-controlled barrier or gate is present, typically requiring a valid ticket or pass to pass through.
-
E.
parkEntranceStation
Indicates that a location functions as an entrance station or access point for a park.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7199bd6788190b0eb050636b84168 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2:01 a.m.