Triple
T35359366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donald |
E1021429
|
entity |
| Predicate | hasParkingStructureType |
P3380
|
FINISHED |
| Object | multi-level parking structure section |
—
|
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: multi-level parking structure section | Statement: [Donald, hasParkingStructureType, multi-level parking structure section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParkingStructureType Context triple: [Donald, hasParkingStructureType, multi-level parking structure section]
-
A.
parkingStructure
Indicates that one entity is a parking facility or structure associated with another entity (such as a building, location, or organization).
-
B.
hasParking
Indicates that a place or facility provides designated parking space(s) available for use.
-
C.
parkingType
chosen
Indicates the specific kind or category of parking arrangement associated with an entity (e.g., street, garage, lot, reserved).
-
D.
hasParkingFor
Indicates that a place or facility provides designated parking spaces suitable for a specified type of vehicle or user.
-
E.
hasUndergroundParking
Indicates that a place or building provides parking facilities located below ground level.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.