Triple
T27765017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schlesinger & Mayer |
E701576
|
entity |
| Predicate | flagshipBuilding |
P126465
|
FINISHED |
| Object | Sullivan Center |
—
|
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: Sullivan Center | Statement: [Schlesinger & Mayer, flagshipBuilding, Sullivan Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagshipBuilding Context triple: [Schlesinger & Mayer, flagshipBuilding, Sullivan Center]
-
A.
flagshipBuildingListedOn
Indicates that a particular flagship building is officially recorded or registered on a specified list or registry.
-
B.
foundingBuilding
Indicates that a particular building is the original or primary structure where an organization, institution, or entity was founded.
-
C.
flagshipStoreBuildingArchitect
Indicates the architect who designed the building that houses the flagship store.
-
D.
flagshipStoreBuildingUse
chosen
Indicates that a building is used as the primary or flagship retail store location for a brand or company.
-
E.
capitalBuilding
Indicates that a building serves as the primary governmental or administrative center (capital building) for a political region or entity.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 4:30 p.m.