Triple
T29989247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Trust Company branch buildings |
E761824
|
entity |
| Predicate | architecturalFirmHeadquartersCity |
P148628
|
FINISHED |
| Object | Cleveland |
—
|
NE NERFINISHED |
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: Cleveland | Statement: [Cleveland Trust Company branch buildings, architecturalFirmHeadquartersCity, Cleveland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalFirmHeadquartersCity Context triple: [Cleveland Trust Company branch buildings, architecturalFirmHeadquartersCity, Cleveland]
-
A.
architecturalFirmHeadquarters
chosen
Indicates the location where an architectural firm’s main offices or central headquarters are based.
-
B.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
C.
laterCompanyHeadquartersCity
Indicates that the specified city is the location of a company’s headquarters during a later period in time, following an earlier headquarters location.
-
D.
sponsorHeadquartersCity
Indicates the city where the sponsoring organization’s main headquarters is located.
-
E.
employerHeadquarters
Indicates the location where an employer’s main corporate offices or central administrative operations are based.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 6:37 p.m.