Triple
T33447160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin Center |
E856537
|
entity |
| Predicate | isMajorOfficeHubFor |
P146066
|
FINISHED |
| Object | downtown Chicago |
—
|
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: downtown Chicago | Statement: [Franklin Center, isMajorOfficeHubFor, downtown Chicago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorOfficeHubFor Context triple: [Franklin Center, isMajorOfficeHubFor, downtown Chicago]
-
A.
isOfficeHubOf
chosen
Indicates that a location serves as the central office or main administrative hub for a specified organization or area.
-
B.
isMajorOfficeBuildingIn
Indicates that a building is a primary or significant office structure located within a specified geographic or administrative area.
-
C.
mentionsOffice
Indicates that one entity explicitly refers to or brings up an office (such as a workplace, office location, or office role) in relation to another entity.
-
D.
hasOfficeType
Indicates that an entity’s office is classified as a specific type or category of office.
-
E.
worksWithOffice
Indicates that an entity collaborates or is professionally associated with a particular office or office-based organization.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 1, 2026, 1:37 a.m.