Triple
T9260871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodger Stadium Express bus |
E222573
|
entity |
| Predicate | dropoffLocation |
P85353
|
FINISHED |
| Object | Dodger Stadium parking lot |
—
|
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 lot | Statement: [Dodger Stadium Express bus, dropoffLocation, Dodger Stadium parking lot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dropoffLocation Context triple: [Dodger Stadium Express bus, dropoffLocation, Dodger Stadium parking lot]
-
A.
dropOffOption
Indicates an available method or arrangement by which something can be left or delivered at a specified location.
-
B.
dropOffOptions
Indicates the available ways, locations, or conditions under which something can be dropped off or delivered.
-
C.
locationOfDelivery
chosen
Indicates the place or address where an item, service, or shipment is to be delivered.
-
D.
hasDropOffArea
Indicates that an entity provides a designated area where items, passengers, or goods can be temporarily left or unloaded.
-
E.
pickupType
Indicates the manner or method by which an item or person is collected or retrieved (e.g., in-store pickup, curbside, scheduled pickup).
- 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_69ca841f2e808190a64f4c31903a1332 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07175be881908a917573ec9b9081 |
completed | April 1, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:32 p.m.