Triple
T8350033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B1 |
E196135
|
entity |
| Predicate | productionStartApprox |
P31468
|
FINISHED |
| Object | 1973 |
—
|
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: 1973 | Statement: [B1, productionStartApprox, 1973]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionStartApprox Context triple: [B1, productionStartApprox, 1973]
-
A.
productionEnd
Indicates that a production process, activity, or run has come to its completion or final stopping point.
-
B.
productionStartForG20
Indicates that the production start event is associated with or applies to a G20 entity or context.
-
C.
massProductionStart
chosen
Indicates the point in time when an item or product begins to be manufactured at large scale in a mass-production process.
-
D.
beganCommercialProduction
Indicates that an entity started producing something commercially, marking the commencement of its large-scale or market-oriented production.
-
E.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
- 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_69ca82edd63c8190b876b8465464c5fa |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80181ca48190bbf2e6a6aae80d69 |
completed | March 31, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.