Triple
T30925170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Station–Dodger Stadium |
E787835
|
entity |
| Predicate | hasDropOffLocation |
P24210
|
FINISHED |
| Object | Dodger Stadium parking areas |
—
|
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: Dodger Stadium parking areas | Statement: [Union Station–Dodger Stadium, hasDropOffLocation, Dodger Stadium parking areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDropOffLocation Context triple: [Union Station–Dodger Stadium, hasDropOffLocation, Dodger Stadium parking areas]
-
A.
hasDropOffArea
chosen
Indicates that an entity provides a designated area where items, passengers, or goods can be temporarily left or unloaded.
-
B.
dropOffOptions
Indicates the available ways, locations, or conditions under which something can be dropped off or delivered.
-
C.
dropOffOption
Indicates an available method or arrangement by which something can be left or delivered at a specified location.
-
D.
hasDropOffDepth
Indicates the depth at which something is dropped off or delivered relative to a reference surface or location.
-
E.
hasPickup
Indicates that one entity is assigned or associated with a specific pickup location, time, or arrangement for collection.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:51 p.m.