Triple
T16825436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISDN |
E409006
|
entity |
| Predicate | commercialDeploymentBegan |
P35191
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [ISDN, commercialDeploymentBegan, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialDeploymentBegan Context triple: [ISDN, commercialDeploymentBegan, 1980s]
-
A.
beganCommercialProduction
Indicates that an entity started producing something commercially, marking the commencement of its large-scale or market-oriented production.
-
B.
commercialAvailability
Indicates that an entity is offered for sale or otherwise obtainable through commercial channels.
-
C.
openedForCommercialService
chosen
Indicates that something (such as a facility, route, or service) began operating and became available for regular commercial use.
-
D.
firstCommercialUse
Indicates the earliest point in time at which something was used commercially or put into commercial operation.
-
E.
firstDeployedAt
Indicates the date and time when an entity was initially put into use or made operational.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b3126db88190ac5595b0d50e4232 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.