Triple
T28835368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Generations |
E728165
|
entity |
| Predicate | workLocationOfProduction |
P110586
|
FINISHED |
| Object | Johannesburg |
—
|
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: Johannesburg | Statement: [Generations, workLocationOfProduction, Johannesburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workLocationOfProduction Context triple: [Generations, workLocationOfProduction, Johannesburg]
-
A.
placeOfOriginOfWork
chosen
Indicates the location where a work (such as an artwork, literary piece, or other creation) was originally produced or created.
-
B.
locationOfWork
Indicates the place or site where an entity performs its work or carries out its professional activities.
-
C.
hasPrimaryProductionLocation
Indicates that an entity’s main or principal place where it is produced or manufactured is a specified location.
-
D.
locationInWork
Indicates that one entity specifies the place or setting where another entity occurs, is situated, or takes place within a particular work (e.g., a scene’s location in a film or a chapter’s setting in a book).
-
E.
commissionedWorkLocation
Indicates the place where a commissioned work is created, produced, or carried out.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596d86b4819092d7d7131ca42cf8 |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:39 a.m.