Triple
T26465595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raleigh Entertainment & Sports Arena |
E665753
|
entity |
| Predicate | parkingCapacityApprox |
P21999
|
FINISHED |
| Object | 7000 |
—
|
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: 7000 | Statement: [Raleigh Entertainment & Sports Arena, parkingCapacityApprox, 7000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkingCapacityApprox Context triple: [Raleigh Entertainment & Sports Arena, parkingCapacityApprox, 7000]
-
A.
numberOfParkingSpaces
chosen
Indicates the total count of parking spaces associated with a particular entity or location.
-
B.
typicalParkingDepth
Indicates the usual or standard depth measurement associated with a parking space or parking area.
-
C.
passengersCountApproximate
Indicates that the number of passengers involved is given as an approximate or estimated count rather than an exact figure.
-
D.
hasUndergroundParking
Indicates that a place or building provides parking facilities located below ground level.
-
E.
hasParking
Indicates that a place or facility provides designated parking space(s) available for use.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612996ea48190913110dfba86cdbd |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:15 a.m.