Triple
T16560283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K6 red telephone kiosk |
E402318
|
entity |
| Predicate | productionBegan |
P52527
|
FINISHED |
| Object | 1936 |
—
|
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: 1936 | Statement: [K6 red telephone kiosk, productionBegan, 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionBegan Context triple: [K6 red telephone kiosk, productionBegan, 1936]
-
A.
beganCommercialProduction
Indicates that an entity started producing something commercially, marking the commencement of its large-scale or market-oriented production.
-
B.
productionStartApproximate
Indicates that the start of production for something is known only approximately rather than as an exact date or time.
-
C.
firstProducedAt
Indicates the location or context where something was originally created, manufactured, or brought into existence for the first time.
-
D.
massProductionStart
Indicates the point in time when an item or product begins to be manufactured at large scale in a mass-production process.
-
E.
producedOn
chosen
Indicates that something was created, manufactured, or brought into existence at a specific date or time.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576d88288190b33543bea4706a36 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.