Triple
T3617140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pico-Union |
E76629
|
entity |
| Predicate | containsBuildingType |
P50464
|
FINISHED |
| Object | early 20th-century single-family homes |
—
|
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: early 20th-century single-family homes | Statement: [Pico-Union, containsBuildingType, early 20th-century single-family homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsBuildingType Context triple: [Pico-Union, containsBuildingType, early 20th-century single-family homes]
-
A.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
B.
hasBuildingHeightType
Indicates the classification or type used to characterize the height of a building in the relationship.
-
C.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
D.
hasBuildingFunction
Indicates that a building is used for or serves a particular function or purpose.
-
E.
hasBuildingForm
Indicates that an entity possesses or is characterized by a particular architectural or structural building form.
- F. None of above. chosen
Provenance (4 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27dd030819083d34fee0c06612a |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9bbb62c8190989629ca11733e1b |
completed | March 8, 2026, 6:02 p.m. |
Created at: March 8, 2026, 3:23 p.m.