Triple
T33637422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore Orioles Hall of Fame |
E861733
|
entity |
| Predicate | physicalDisplayLocation |
P76038
|
FINISHED |
| Object | Oriole Park at Camden Yards concourse |
—
|
NE NERFINISHED |
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: Oriole Park at Camden Yards concourse | Statement: [Baltimore Orioles Hall of Fame, physicalDisplayLocation, Oriole Park at Camden Yards concourse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physicalDisplayLocation Context triple: [Baltimore Orioles Hall of Fame, physicalDisplayLocation, Oriole Park at Camden Yards concourse]
-
A.
currentDisplayLocation
Indicates the location or context where something is presently being shown or rendered.
-
B.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
C.
isPhysicalLocation
Indicates that one entity serves as a physical, real-world place or site associated with another entity.
-
D.
objectLocation
chosen
Indicates that one entity is located at, in, or on another entity or spatial region.
-
E.
printLocation
Indicates the place or medium where something is printed or made publicly available in printed form.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.