Triple
T4031805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5ESS switch |
E83730
|
entity |
| Predicate | commercialDeploymentStart |
P35191
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [5ESS switch, commercialDeploymentStart, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialDeploymentStart Context triple: [5ESS switch, commercialDeploymentStart, 1982]
-
A.
commercialLaunchFirst
Indicates that this event marks the first commercial launch associated with the subject entity.
-
B.
developmentStart
Indicates the point in time or event when the development process of something begins.
-
C.
openedForCommercialService
chosen
Indicates that something (such as a facility, route, or service) began operating and became available for regular commercial use.
-
D.
commercialOperationStartUnit1
Indicates the date or time when commercial operation of Unit 1 begins.
-
E.
commercialOperationStartUnit2
Indicates the point in time when the second unit of a facility or system begins its commercial operation.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb0dbb8481909ff2ee49dadcd1dc |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.