Triple
T15362174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Federal Center |
E367313
|
entity |
| Predicate | plazaSurface |
P47694
|
FINISHED |
| Object | granite-paved plaza |
—
|
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: granite-paved plaza | Statement: [Chicago Federal Center, plazaSurface, granite-paved plaza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plazaSurface Context triple: [Chicago Federal Center, plazaSurface, granite-paved plaza]
-
A.
hasPlaza
Indicates that an entity includes, contains, or is associated with a plaza as part of its structure or grounds.
-
B.
hasPedestrianPlazaOn
Indicates that a pedestrian plaza is located on, or directly associated with, a specified surface, structure, or area.
-
C.
surfaceFeatureOf
chosen
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
D.
helipadSurface
Indicates that one entity serves as the surface material or type of surface for a helipad associated with another entity.
-
E.
laneSurface
Indicates the type or condition of the surface that makes up a lane used for travel or traffic.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e479f188190bbbc3dcd73853e02 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.