Triple
T1369844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chavez Ravine |
E30087
|
entity |
| Predicate | featureWithin |
P12261
|
FINISHED |
| Object | Dodger Stadium parking lots |
—
|
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 lots | Statement: [Chavez Ravine, featureWithin, Dodger Stadium parking lots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureWithin Context triple: [Chavez Ravine, featureWithin, Dodger Stadium parking lots]
-
A.
withinFeature
chosen
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
-
B.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
C.
featureOfInterest
Indicates the entity or object that is the primary subject or focus of the described observation, measurement, or analysis.
-
D.
formsFeature
Indicates that one entity constitutes or creates a characteristic, component, or distinguishing element of another entity.
-
E.
searchFeature
Indicates that an entity provides or supports functionality for searching or querying information or items.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d60fdc8190a9954b74ca2b2541 |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.