Triple
T4814044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eutaw Street concourse |
E107141
|
entity |
| Predicate | isAccessibleWithTicket |
P5937
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eutaw Street concourse, isAccessibleWithTicket, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAccessibleWithTicket Context triple: [Eutaw Street concourse, isAccessibleWithTicket, true]
-
A.
hasTicketInspection
Indicates that a ticket is checked or verified by an authorized inspector or system.
-
B.
hasTicketRequirement
chosen
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
-
C.
hasTicketBarrier
Indicates that an access-controlled barrier or gate is present, typically requiring a valid ticket or pass to pass through.
-
D.
hasTicketIntegration
Indicates that there is an established connection enabling ticket-related data or actions to be shared or synchronized between systems or components.
-
E.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
- 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_69bd43f779448190b92885cb70abb6c2 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1dfa3481909d240d50ed0ee38c |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.