Triple
T31672476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudolf Schindler |
E808306
|
entity |
| Predicate | primaryWorkRegion |
P207493
|
FINISHED |
| Object | Southern California |
E716
|
NE 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: Southern California | Statement: [Rudolf Schindler, primaryWorkRegion, Southern California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryWorkRegion Context triple: [Rudolf Schindler, primaryWorkRegion, Southern California]
-
A.
traditionalRegionOfResidence
Indicates the customary or historically established geographic region where an entity (typically a person or group) resides or is considered to be from.
-
B.
homeCityRegion
Indicates the city or broader regional area that serves as an entity’s primary place of residence or origin.
-
C.
homeCityMetropolitanArea
Indicates that a specified city serves as the primary metropolitan area associated with a given entity’s home location.
-
D.
primaryUseCity
Indicates that a city is the main or principal location where something (such as a service, facility, or entity) is primarily used or operates.
-
E.
primaryLocationCity
Indicates the city that serves as the main or primary location associated with the subject.
- F. None of above. chosen
Provenance (5 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b79f4b4708190bf579fc7fa4bf0e4 |
completed | June 12, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 11:01 p.m.