Triple
T30033233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LECOM Park |
E763079
|
entity |
| Predicate | hasGrandstandOrientation |
P152859
|
FINISHED |
| Object | faces northeast |
—
|
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: faces northeast | Statement: [LECOM Park, hasGrandstandOrientation, faces northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrandstandOrientation Context triple: [LECOM Park, hasGrandstandOrientation, faces northeast]
-
A.
hasGrandstandFeature
Indicates that something possesses or includes a grandstand-related feature or characteristic.
-
B.
hasGrandstandStyle
Indicates that something is characterized by or associated with a particular style or type of grandstand.
-
C.
stadiumOrientation
chosen
Indicates the directional alignment or layout of a stadium relative to a reference (e.g., compass directions or surrounding features).
-
D.
hasBleacherSeating
Indicates that a venue or location is equipped with bleacher-style seating for spectators.
-
E.
stadiumFeature
Indicates that a stadium possesses or includes a particular feature, characteristic, or facility.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 29, 2026, 6:50 p.m.