Triple
T1997393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salesforce Tower vicinity |
E43389
|
entity |
| Predicate | dominantBuildingUse |
P14072
|
FINISHED |
| Object | office |
—
|
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: office | Statement: [Salesforce Tower vicinity, dominantBuildingUse, office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantBuildingUse Context triple: [Salesforce Tower vicinity, dominantBuildingUse, office]
-
A.
primaryLandUse
chosen
Indicates the main or dominant way in which a given piece of land is utilized or designated (e.g., residential, agricultural, commercial).
-
B.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
C.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
-
D.
architecturalUse
Indicates how a structure, space, or element is intended to be used or function within an architectural context.
-
E.
architectureProperty
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb79c97d48190b3147430ed39faa9 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.