Triple
T24464033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewelry District, Los Angeles |
E616915
|
entity |
| Predicate | approximateEraOfDevelopment |
P53319
|
FINISHED |
| Object | early 20th century |
—
|
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 | Statement: [Jewelry District, Los Angeles, approximateEraOfDevelopment, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateEraOfDevelopment Context triple: [Jewelry District, Los Angeles, approximateEraOfDevelopment, early 20th century]
-
A.
approximateCompletionEra
chosen
Indicates the general historical period or time range during which something was completed, without specifying an exact date.
-
B.
developedFromPeriod
Indicates that something originated, evolved, or was derived from a specified historical or temporal period.
-
C.
yearOfDevelopment
Indicates the specific year in which something was developed or created.
-
D.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
E.
associatedProductionEra
Indicates a relationship where something is linked to the specific time period or era during which it was produced or created.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298cc60448190a5383d452f563834 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:19 a.m.